Is there a way to get version from package.json in nodejs code?

node.js npm version versioning
Abhik Bose Pramanik picture Abhik Bose Pramanik · Feb 5, 2012 · Viewed 281k times · Source

Is there a way to get the version set in package.json in a nodejs app? I would want something like this

var port = process.env.PORT || 3000
app.listen port
console.log "Express server listening on port %d in %s mode %s", app.address().port, app.settings.env, app.VERSION

Answer

Mark Wallace picture Mark Wallace · Jun 1, 2012

I found that the following code fragment worked best for me. Since it uses require to load the package.json, it works regardless the current working directory.

var pjson = require('./package.json');
console.log(pjson.version);

A warning, courtesy of @Pathogen:

Doing this with Browserify has security implications.
Be careful not to expose your package.json to the client, as it means that all your dependency version numbers, build and test commands and more are sent to the client.
If you're building server and client in the same project, you expose your server-side version numbers too. Such specific data can be used by an attacker to better fit the attack on your server.

Related questions

How can I specify the required Node.js version in package.json?

I have a Node.js project that requires Node version 12 or higher. Is there a way to specify this in the packages.json file, so that the installer will automatically check and inform the users if they need to upgrade?

Read More
Node - was compiled against a different Node.js version using NODE_MODULE_VERSION 51

I am running a node application on terminal. Have recently upgraded to node v8.5.0, but am getting this error: Error: The module '/tidee/tidee-au/packages/tidee-au-server/node_modules/bcrypt/lib/binding/bcrypt_lib.node' was compiled against a different …

Read More
Make `npm install --save` add a strict version to package.json

When you run npm install --save somepackage, it usually adds something like this into package.json: "dependencies": { "somepackage": "^2.1.0" } Because the version is prepended with a caret(^), this means that if you later run npm install, it might install version 2.3.0 instead. …

Read More