There are a lot of details in the File System API. The most common way is: const fs = require(‘fs’); fs.writeFile(“/tmp/test”, “Hey there!”, function(err) { if(err) { return console.log(err); } console.log(“The file was saved!”); }); // Or fs.writeFileSync(‘/tmp/test-sync’, ‘Hey there!’);
Use: npm update -g npm See the docs for the update command: npm update [-g] [<pkg>…] This command will update all the packages listed to the latest version (specified by the tag config), respecting semver. Additionally, see the documentation on Node.js and NPM installation and Upgrading NPM. The following original answer is from the old … Read more
Call the global process object’s exit method: process.exit() From the docs: process.exit([exitcode]) Ends the process with the specified code. If omitted, exit with a ‘success’ code 0. To exit with a ‘failure’ code: process.exit(1); The shell that executed node should see the exit code as 1.
You did a great job of summarizing what’s awesome about Node.js. My feeling is that Node.js is especially suited for applications where you’d like to maintain a persistent connection from the browser back to the server. Using a technique known as “long-polling”, you can write an application that sends updates to the user in real … Read more
Yes, package-lock.json is intended to be checked into source control. If you’re using npm 5+, you may see this notice on the command line: created a lockfile as package-lock.json. You should commit this file. According to npm help package-lock.json: package-lock.json is automatically generated for any operations where npm modifies either the node_modules tree, or package.json. … Read more
Looks like npm-check-updates is the only way to make this happen now. npm i -g npm-check-updates ncu -u npm install On npm <3.11: Simply change every dependency’s version to *, then run npm update –save. (Note: broken in recent (3.11) versions of npm). Before: “dependencies”: { “express”: “*”, “mongodb”: “*”, “underscore”: “*”, “rjs”: “*”, “jade”: … Read more
You can try netstat netstat -vanp tcp | grep 3000 For macOS El Capitan and newer (or if your netstat doesn’t support -p), use lsof lsof -i tcp:3000
Sure the code does work, but I’m pretty sure it doesn’t do what you expect it to do. It just fires off multiple asynchronous calls, but the printFiles function does immediately return after that. Reading in sequence If you want to read the files in sequence, you cannot use forEach indeed. Just use a modern … Read more
Summary of important behavior differences: dependencies are installed on both: npm install from a directory that contains package.json npm install $package on any other directory devDependencies are: also installed on npm install on a directory that contains package.json, unless you pass the –production flag (go upvote Gayan Charith’s answer), or if the NODE_ENV=production environment variable … Read more
Use npm list for local packages or npm list -g for globally installed packages. You can find the version of a specific package by passing its name as an argument. For example, npm list grunt will result in: projectName@projectVersion /path/to/project/folder └── grunt@0.4.1 Alternatively, you can just run npm list without passing a package name as … Read more