The accepted answer did not work for me. Here’s what I’m doing to pull a package from github: npm install –save “git://github.com/username/package.git#commit” Or adding it manually on package.json: “dependencies”: { “package”: “git://github.com/username/package.git#commit” }
__dirname is only defined in scripts. It’s not available in REPL. try make a script a.js console.log(__dirname); and run it: node a.js you will see __dirname printed. Added background explanation: __dirname means ‘The directory of this script’. In REPL, you don’t have a script. Hence, __dirname would not have any real meaning.
You can just delete the node_module directory rm -rf node_modules/
You can add any Git repository (or tarball) as a dependency to yarn by specifying the remote URL (either HTTPS or SSH): yarn add <git remote url> installs a package from a remote git repository. yarn add <git remote url>#<branch/commit/tag> installs a package from a remote git repository at specific git branch, git commit or … Read more
http.request docs contains example how to receive body of the response through handling data event: var options = { host: ‘www.google.com’, port: 80, path: ‘/upload’, method: ‘POST’ }; var req = http.request(options, function(res) { console.log(‘STATUS: ‘ + res.statusCode); console.log(‘HEADERS: ‘ + JSON.stringify(res.headers)); res.setEncoding(‘utf8’); res.on(‘data’, function (chunk) { console.log(‘BODY: ‘ + chunk); }); }); req.on(‘error’, function(e) … Read more
angular cli can report its version when you run it with the version flag ng –version
sudo apt-get remove nodejs sudo apt-get remove npm Then go to /etc/apt/sources.list.d and remove any node list if you have. Then do a sudo apt-get update Check for any .npm or .node folder in your home folder and delete those. If you type which node you can see the location of the node. Try which … Read more
From the NPM docs on package.json: private If you set “private”: true in your package.json, then npm will refuse to publish it. This is a way to prevent accidental publication of private repositories.
Something like this worked for me. I am guessing this should work for you. Run webpack-dev using this webpack-dev-server –host 0.0.0.0 –port 80 And set this in webpack.config.js entry: [ ‘webpack-dev-server/client?http://0.0.0.0:80’, config.paths.demo ] Note If you are using hot loading, you will have to do this. Run webpack-dev using this webpack-dev-server –host 0.0.0.0 –port 80 … Read more
See https://github.com/npm/npm/issues/16861 This worked for me: npm cache verify Then I re-ran: npm install -g create-react-app And it installed as expected: Issue resolved. Other solutions mentioned in the GitHub issue include: npm cache clean –force OR Deleting npm and npm-cache folders in Users%username%\AppData\Roaming (Windows 7 and Windows 10) and running npm install OR Update npm … Read more