I found that the following code fragment worked best for me. Since it uses require to load the package.json, it works regardless of 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 … Read more
It’s part of the ES6 module system, described here. There is a helpful example in that documentation, also: If a module defines a default export: // foo.js export default function() { console.log(“hello!”) } then you can import that default export by omitting the curly braces: import foo from “foo”; foo(); // hello! Update: As of … Read more
In Node.js, you can use util.inspect(object). It automatically replaces circular links with “[Circular]”. Albeit being built-in (no installation is required), you must import it import * as util from ‘util’ // has no default export import { inspect } from ‘util’ // or directly // or var util = require(‘util’) To use it, simply call … Read more
Even though question has been answered and accepted long ago, i just want to share my 2 cents: You can imagine that at the very beginning of your file there is something like (just for explanation): var module = new Module(…); var exports = module.exports; So whatever you do just keep in mind that module.exports … Read more
Promises have state, they start as pending and can settle to: fulfilled meaning that the computation completed successfully. rejected meaning that the computation failed. Promise returning functions should never throw, they should return rejections instead. Throwing from a promise returning function will force you to use both a } catch { and a .catch. People … Read more
You can use process.stdout.write(): process.stdout.write(“hello: “); See the docs for details.
Update 3: As other answers point out as well, the npm ci command got introduced in npm 5.7.0 as additional way to achieve fast and reproducible builds in the CI context. See the documentation and npm blog for further information. Update 2: The issue to update and clarify the documentation is GitHub issue #18103. Update … Read more
Below you can find colors reference of text to command when running node.js application: console.log(‘\x1b[36m%s\x1b[0m’, ‘I am cyan’); //cyan console.log(‘\x1b[33m%s\x1b[0m’, stringToMakeYellow); //yellow Note %s is where in the string (the second argument) gets injected. \x1b[0m resets the terminal color so it doesn’t continue to be the chosen color anymore after this point. Colors reference Reset … Read more
Things have changed once again starting Express 4.16.0, you can now use express.json() and express.urlencoded() just like in Express 3.0. This was different starting Express 4.0 to 4.15: $ npm install –save body-parser and then: var bodyParser = require(‘body-parser’) app.use( bodyParser.json() ); // to support JSON-encoded bodies app.use(bodyParser.urlencoded({ // to support URL-encoded bodies extended: true … Read more
npm list -g –depth=0 npm: the Node.js package manager command line tool list -g: display a tree of every package found in the user’s folders (without the -g option it only shows the current directory’s packages) –depth 0 / –depth=0: avoid including every package’s dependencies in the tree view