It’s often useful to have an application know about itself: you can use the current version to identify data for required for migrations, expose a list of libraries you use for debugging purposes, or create screens that show end users license and author information for your application.<\/p>\n
In a node script, you can pull this information by importing your own package.json:<\/p>\n
\nlet me = require('.\/package.json');\nlet version = me.version,\n author = me.author,\n dependencies = me.dependencies;\n<\/pre>\nThis is an example output:<\/p>\n
\nGary Sieling\n1.0.0\n{ async: '^2.0.0-rc.1',\n bluebird: '^3.3.4',\n dropzone: '^4.3.0',\n 'eventsource-polyfill': '^0.9.6',\n express: '^4.13.4',\n 'express-http-proxy': '^0.6.0',\n jquery: '^2.2.1',\n jsx: '^0.9.89',\n lodash: '^4.5.1',\n morgan: '^1.7.0',\n react: '^0.14.7',\n 'react-bootstrap': '^0.28.3',\n 'react-dom': '^0.14.7',\n 'react-router': '^2.0.0',\n request: '^2.69.0',\n 'request-promise': '^2.0.1',\n webpack: '^1.8.11',\n 'webpack-dev-middleware': '*',\n 'webpack-hot-middleware': '^2.7.1' }\n<\/pre>\n","protected":false},"excerpt":{"rendered":"It’s often useful to have an application know about itself: you can use the current version to identify data for required for migrations, expose a list of libraries you use for debugging purposes, or create screens that show end users license and author information for your application. In a node script, you can pull this … <\/p>\n