Updating and Configuring NPM; installing all Packages (approximately 400,000), Dependencies/Library

Have followed all tutorials including returns from the bash terminal on installing NPM updates; including packages and dependencies.  Terminal returns: you can update NPM 5.5.1 to 5.6.0., however, it won’t update even after issuing commands in different formats (according to tutorials).  I’m missing packages, the directory, library, and dependencies of anything over 5.5.1.  NPM returns generic responses, even after I issue specific commands (and use specific language).  I started agreeing with its returns, e.g. (“yes, update”), just to get through it.  See example below where I asked NPM to clone NPM direcotory, where NPM responded with “did you mean update”.  I responded “yes, update” because it would produce returns inconsistent with direct commands. Of course, I didn’t mean UPDATE in that particular example, but I felt I had no choice but to say “update.” Very seldom NPM returns responses consistent and specific to the command language utilized, and according to what tutorials say the return should be.  

NPM (5.5.1) doesn’t let me configure from the terminal, it constantly refers me back to use my local usr files for configuration; not ever giving me the option to execute configuration through the terminal (again, using command language instructed by the tutorials). I sometimes get a better result when I design or orchestrate my own command language.

In the past, I’ve also asked NPM to update and/or upgrade according to tutorial language (not referring to example below), and NPM will return responses such as, “did you mean test”, or “tst”, or “view”, (some inappropriate response to the command issued - again, using command language generated by tutorials).

The following is a weak example of the exchanges between myself and NPM (terminal). I’m not sure why the terminal uses my iphone, or even Haxe in their responses.  It started using Haxe and iphone (iphone:Haxe) just recently, even when I attempt to communicate outside of Haxe:


pm@5.5.1 /usr/local/lib/node\_modules/npm  
iphone:Haxe yvonnemcginnis$ npm install all packages and documents on RunKit which arepublic and non-restrictive.  
npm ERR! code E404  
npm ERR! 404 Not Found: RunKit@latest

npm ERR! A complete log of this run can be found in:  
npm ERR! /Users/yvonnemcginnis/.npm/\_logs/2018-01-03T20\_16\_23\_729Z-debug.log  
iphone:Haxe yvonnemcginnis$ npm rquire() any missing packages directly from npm.  
bash: syntax error near unexpected token `('  
iphone:Haxe yvonnemcginnis$ var Commands = require('commands.js');  
bash: syntax error near unexpected token `('  
iphone:Haxe yvonnemcginnis$ console.log( Commands.get('someArg') ); // outputs "foo"  
bash: syntax error near unexpected token `Commands.get'  
iphone:Haxe yvonnemcginnis$ console.log( Commands.get('someUnknownArg', 'defaultValue') ); // outputs "defaultValue"  
bash: syntax error near unexpected token `Commands.get'  
iphone:Haxe yvonnemcginnis$ console.log( Commands.exists('someUnknownArg') ); // outputs false  
bash: syntax error near unexpected token `Commands.exists'  
iphone:Haxe yvonnemcginnis$ console.log( Commands.get('bar') ); // outputs true  
bash: syntax error near unexpected token `Commands.get'  
iphone:Haxe yvonnemcginnis$ console.log( Commands.get('baz') ); // outputs false  
bash: syntax error near unexpected token `Commands.get'  
iphone:Haxe yvonnemcginnis$  
iphone:Haxe yvonnemcginnis$ \> node script.js -some-arg "foo" --bar --no-baz  
bash: script.js: command not found  
iphone:Haxe yvonnemcginnis$ npm install config.json.  
npm ERR! code E404  
npm ERR! 404 Not Found: config.json.@latest

npm ERR! A complete log of this run can be found in:  
npm ERR! /Users/yvonnemcginnis/.npm/\_logs/2018-01-03T20\_22\_36\_997Z-debug.log  
iphone:Haxe yvonnemcginnis$ {  
\> "domain": "[www.example.com](http://www.example.com)",  
\> "mongodb": {  
\> "host": "localhost",  
\> "port": 27017  
\> }  
bash: domain:: command not found  
bash: mongodb:: command not found  
bash: host:: command not found  
bash: port:: command not found  
iphone:Haxe yvonnemcginnis$ }  
bash: syntax error near unexpected token `}'  
iphone:Haxe yvonnemcginnis$ {  
\> "domain": "dev.example.com"  
\> }  
bash: domain:: command not found  
iphone:Haxe yvonnemcginnis$ npm test config by vi sample.js.  
npm ERR! path /Users/yvonnemcginnis/package.json  
npm ERR! code ENOENT  
npm ERR! errno -2  
npm ERR! syscall open  
npm ERR! enoent ENOENT: no such file or directory, open '/Users/yvonnemcginnis/package.json'  
npm ERR! enoent This is related to npm not being able to find a file.  
npm ERR! enoent

npm ERR! A complete log of this run can be found in:  
npm ERR! /Users/yvonnemcginnis/.npm/\_logs/2018-01-03T20\_25\_03\_100Z-debug.log  
iphone:Haxe yvonnemcginnis$ npm install npm\_dir.  
npm ERR! code E404  
npm ERR! 404 Not Found: npm\_dir.@latest

npm ERR! A complete log of this run can be found in:  
npm ERR! /Users/yvonnemcginnis/.npm/\_logs/2018-01-03T20\_26\_56\_004Z-debug.log  
iphone:Haxe yvonnemcginnis$ npm clone npm\_directory.

Usage: npm \<command\>

where \<command\> is one of:  
access, adduser, bin, bugs, c, cache, completion, config,  
ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,  
explore, get, help, help-search, i, init, install,  
install-test, it, link, list, ln, login, logout, ls,  
outdated, owner, pack, ping, prefix, profile, prune,  
publish, rb, rebuild, repo, restart, root, run, run-script,  
s, se, search, set, shrinkwrap, star, stars, start, stop, t,  
team, test, token, tst, un, uninstall, unpublish, unstar,  
up, update, v, version, view, whoami

npm \<command\> -h quick help on \<command\>  
npm -l display full usage info  
npm help \<term\> search for help on \<term\>  
npm help npm involved overview

Specify configs in the ini-formatted file:  
/Users/yvonnemcginnis/.npmrc  
or on the command line via: npm \<command\> --key value  
Config info can be viewed via: npm help config

npm@5.5.1 /usr/local/lib/node\_modules/npm  
iphone:Haxe yvonnemcginnis$ npm create nps-cache-dir.

Usage: npm \<command\>

where \<command\> is one of:  
access, adduser, bin, bugs, c, cache, completion, config,  
ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,  
explore, get, help, help-search, i, init, install,  
install-test, it, link, list, ln, login, logout, ls,  
outdated, owner, pack, ping, prefix, profile, prune,  
publish, rb, rebuild, repo, restart, root, run, run-script,  
s, se, search, set, shrinkwrap, star, stars, start, stop, t,  
team, test, token, tst, un, uninstall, unpublish, unstar,  
up, update, v, version, view, whoami

npm \<command\> -h quick help on \<command\>  
npm -l display full usage info  
npm help \<term\> search for help on \<term\>  
npm help npm involved overview

Specify configs in the ini-formatted file:  
/Users/yvonnemcginnis/.npmrc  
or on the command line via: npm \<command\> --key value  
Config info can be viewed via: npm help config

npm@5.5.1 /usr/local/lib/node\_modules/npm

Did you mean this?  
update  
iphone:Haxe yvonnemcginnis$ npm create, update, creating an object representation of adirectory tree.

Usage: npm \<command\>

where \<command\> is one of:  
access, adduser, bin, bugs, c, cache, completion, config,  
ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,  
explore, get, help, help-search, i, init, install,  
install-test, it, link, list, ln, login, logout, ls,  
outdated, owner, pack, ping, prefix, profile, prune,  
publish, rb, rebuild, repo, restart, root, run, run-script,  
s, se, search, set, shrinkwrap, star, stars, start, stop, t,  
team, test, token, tst, un, uninstall, unpublish, unstar,  
up, update, v, version, view, whoami

npm \<command\> -h quick help on \<command\>  
npm -l display full usage info  
npm help \<term\> search for help on \<term\>  
npm help npm involved overview

Specify configs in the ini-formatted file:  
/Users/yvonnemcginnis/.npmrc  
or on the command line via: npm \<command\> --key value  
Config info can be viewed via: npm help config

npm@5.5.1 /usr/local/lib/node\_modules/npm  
iphone:Haxe yvonnemcginnis$ npm create an object representation of a directory tree, npm-max-dir-index.

Usage: npm \<command\>

where \<command\> is one of:  
access, adduser, bin, bugs, c, cache, completion, config,  
ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,  
explore, get, help, help-search, i, init, install,  
install-test, it, link, list, ln, login, logout, ls,  
outdated, owner, pack, ping, prefix, profile, prune,  
publish, rb, rebuild, repo, restart, root, run, run-script,  
s, se, search, set, shrinkwrap, star, stars, start, stop, t,  
team, test, token, tst, un, uninstall, unpublish, unstar,  
up, update, v, version, view, whoami

npm \<command\> -h quick help on \<command\>  
npm -l display full usage info  
npm help \<term\> search for help on \<term\>  
npm help npm involved overview

Specify configs in the ini-formatted file:  
/Users/yvonnemcginnis/.npmrc  
or on the command line via: npm \<command\> --key value  
Config info can be viewed via: npm help config

npm@5.5.1 /usr/local/lib/node\_modules/npm

Did you mean this?  
update  
iphone:Haxe yvonnemcginnis$ npm update.

Usage: npm \<command\>

where \<command\> is one of:  
access, adduser, bin, bugs, c, cache, completion, config,  
ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,  
explore, get, help, help-search, i, init, install,  
install-test, it, link, list, ln, login, logout, ls,  
outdated, owner, pack, ping, prefix, profile, prune,  
publish, rb, rebuild, repo, restart, root, run, run-script,  
s, se, search, set, shrinkwrap, star, stars, start, stop, t,  
team, test, token, tst, un, uninstall, unpublish, unstar,  
up, update, v, version, view, whoami

npm \<command\> -h quick help on \<command\>  
npm -l display full usage info  
npm help \<term\> search for help on \<term\>  
npm help npm involved overview

Specify configs in the ini-formatted file:  
/Users/yvonnemcginnis/.npmrc  
or on the command line via: npm \<command\> --key value  
Config info can be viewed via: npm help config

npm@5.5.1 /usr/local/lib/node\_modules/npm

Did you mean one of these?  
update  
outdated  
iphone:Haxe yvonnemcginnis$ npm-cli-dir-cdn.  
bash: npm-cli-dir-cdn.: command not found  
iphone:Haxe yvonnemcginnis$ npm install generator-nom to update node modules.  
npm ERR! code E404  
npm ERR! 404 Not Found: modules.@latest

npm ERR! A complete log of this run can be found in:  
npm ERR! /Users/yvonnemcginnis/.npm/\_logs/2018-01-03T20\_32\_59\_378Z-debug.log  
iphone:Haxe yvonnemcginnis$ npm install, save, and use all 400,000 npm packages.

Usage: npm \<command\>

where \<command\> is one of:  
access, adduser, bin, bugs, c, cache, completion, config,  
ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,  
explore, get, help, help-search, i, init, install,  
install-test, it, link, list, ln, login, logout, ls,  
outdated, owner, pack, ping, prefix, profile, prune,  
publish, rb, rebuild, repo, restart, root, run, run-script,  
s, se, search, set, shrinkwrap, star, stars, start, stop, t,  
team, test, token, tst, un, uninstall, unpublish, unstar,  
up, update, v, version, view, whoami

npm \<command\> -h quick help on \<command\>  
npm -l display full usage info  
npm help \<term\> search for help on \<term\>  
npm help npm involved overview

Specify configs in the ini-formatted file:  
/Users/yvonnemcginnis/.npmrc  
or on the command line via: npm \<command\> --key value  
Config info can be viewed via: npm help config

npm@5.5.1 /usr/local/lib/node\_modules/npm

Did you mean one of these?  
install  
uninstall  
unstar  
iphone:Haxe yvonnemcginnis$ npm install all 400,000 npm packages.  
npm ERR! code EINVALIDTAGNAME  
npm ERR! Invalid tag name "400,000": Tags may not have any characters that encodeURIComponent encodes.

npm ERR! A complete log of this run can be found in:  
npm ERR! /Users/yvonnemcginnis/.npm/\_logs/2018-01-03T20\_34\_04\_507Z-debug.log  
iphone:Haxe yvonnemcginnis$ npm-run-path.  
bash: npm-run-path.: command not found  
iphone:Haxe yvonnemcginnis$ npm find commands to run-path.  
NAME | DESCRIPTION | AUTHOR | DATE | VERSI  
vigilia | simple command line… | =gibatronic | 2016-03-04 | 1.0.0  
git-go-get | This is a simple… | =brettneese | 2017-11-10 | 1.0.1  
iphone:Haxe yvonnemcginnis$ npm install node v4.  
npm ERR! code E404  
npm ERR! 404 Not Found: v4.@latest

npm ERR! A complete log of this run can be found in:  
npm ERR! /Users/yvonnemcginnis/.npm/\_logs/2018-01-03T20\_39\_05\_978Z-debug.log  
iphone:Haxe yvonnemcginnis$ npm\_config\_prefix=/some/path sh install.sh.  
sh: install.sh.: No such file or directory  
iphone:Haxe yvonnemcginnis$ npm install .sh.  
npm ERR! code ENOLOCAL  
npm ERR! Could not install from ".sh." as it does not contain a package.json file.

╭─────────────────────────────────────╮  
│ │  
│ Update available 5.5.1 → 5.6.0 │  
│ Run npm i -g npm to update │  
│ │  
╰─────────────────────────────────────╯

npm ERR! A complete log of this run can be found in:  
npm ERR! /Users/yvonnemcginnis/.npm/\_logs/2018-01-03T20\_41\_42\_693Z-debug.log  
iphone:Haxe yvonnemcginnis$ npm run, install, and save npm 5.6.0.

Usage: npm \<command\>

where \<command\> is one of:  
access, adduser, bin, bugs, c, cache, completion, config,  
ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,  
explore, get, help, help-search, i, init, install,  
install-test, it, link, list, ln, login, logout, ls,  
outdated, owner, pack, ping, prefix, profile, prune,  
publish, rb, rebuild, repo, restart, root, run, run-script,  
s, se, search, set, shrinkwrap, star, stars, start, stop, t,  
team, test, token, tst, un, uninstall, unpublish, unstar,  
up, update, v, version, view, whoami

npm \<command\> -h quick help on \<command\>  
npm -l display full usage info  
npm help \<term\> search for help on \<term\>  
npm help npm involved overview

Specify configs in the ini-formatted file:  
/Users/yvonnemcginnis/.npmrc  
or on the command line via: npm \<command\> --key value  
Config info can be viewed via: npm help config

npm@5.5.1 /usr/local/lib/node\_modules/npm

Did you mean one of these?  
run  
un  
prune  
iphone:Haxe yvonnemcginnis$ npm run.

Usage: npm \<command\>

where \<command\> is one of:  
access, adduser, bin, bugs, c, cache, completion, config,  
ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,  
explore, get, help, help-search, i, init, install,  
install-test, it, link, list, ln, login, logout, ls,  
outdated, owner, pack, ping, prefix, profile, prune,  
publish, rb, rebuild, repo, restart, root, run, run-script,  
s, se, search, set, shrinkwrap, star, stars, start, stop, t,  
team, test, token, tst, un, uninstall, unpublish, unstar,  
up, update, v, version, view, whoami

npm \<command\> -h quick help on \<command\>  
npm -l display full usage info  
npm help \<term\> search for help on \<term\>  
npm help npm involved overview

Specify configs in the ini-formatted file:  
/Users/yvonnemcginnis/.npmrc  
or on the command line via: npm \<command\> --key value  
Config info can be viewed via: npm help config

npm@5.5.1 /usr/local/lib/node\_modules/npm

Did you mean one of these?  
run  
un  
prune  
iphone:Haxe yvonnemcginnis$ npm, install.  
bash: npm,: command not found  
iphone:Haxe yvonnemcginnis$ npm save 5.6.0.

Usage: npm \<command\>

where \<command\> is one of:  
access, adduser, bin, bugs, c, cache, completion, config,  
ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,  
explore, get, help, help-search, i, init, install,  
install-test, it, link, list, ln, login, logout, ls,  
outdated, owner, pack, ping, prefix, profile, prune,  
publish, rb, rebuild, repo, restart, root, run, run-script,  
s, se, search, set, shrinkwrap, star, stars, start, stop, t,  
team, test, token, tst, un, uninstall, unpublish, unstar,  
up, update, v, version, view, whoami

npm \<command\> -h quick help on \<command\>  
npm -l display full usage info  
npm help \<term\> search for help on \<term\>  
npm help npm involved overview

Specify configs in the ini-formatted file:  
/Users/yvonnemcginnis/.npmrc  
or on the command line via: npm \<command\> --key value  
Config info can be viewed via: npm help config

npm@5.5.1 /usr/local/lib/node\_modules/npm

Did you mean this?  
se  
iphone:Haxe yvonnemcginnis$ npm save.

Usage: npm \<command\>

where \<command\> is one of:  
access, adduser, bin, bugs, c, cache, completion, config,  
ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,  
explore, get, help, help-search, i, init, install,  
install-test, it, link, list, ln, login, logout, ls,  
outdated, owner, pack, ping, prefix, profile, prune,  
publish, rb, rebuild, repo, restart, root, run, run-script,  
s, se, search, set, shrinkwrap, star, stars, start, stop, t,  
team, test, token, tst, un, uninstall, unpublish, unstar,  
up, update, v, version, view, whoami

npm \<command\> -h quick help on \<command\>  
npm -l display full usage info  
npm help \<term\> search for help on \<term\>  
npm help npm involved overview

Specify configs in the ini-formatted file:  
/Users/yvonnemcginnis/.npmrc  
or on the command line via: npm \<command\> --key value  
Config info can be viewed via: npm help config

npm@5.5.1 /usr/local/lib/node\_modules/npm  
iphone:Haxe yvonnemcginnis$ npm\_debug=1 sh install.sh.  
sh: install.sh.: No such file or directory  
iphone:Haxe yvonnemcginnis$ npm install .sh.  
npm ERR! code ENOLOCAL  
npm ERR! Could not install from ".sh." as it does not contain a package.json file.

npm ERR! A complete log of this run can be found in:  
npm ERR! /Users/yvonnemcginnis/.npm/\_logs/2018-01-03T20\_44\_41\_816Z-debug.log  
iphone:Haxe yvonnemcginnis$ npm install 5.6.0 from package.json.  
npm ERR! code E404  
npm ERR! 404 Not Found: 5.6.0@latest

npm ERR! A complete log of this run can be found in:  
npm ERR! /Users/yvonnemcginnis/.npm/\_logs/2018-01-03T20\_46\_02\_134Z-debug.log  
iphone:Haxe yvonnemcginnis$

Hi @yrm64 Thanks for being part of the GitHub Community Forum!

This post was moved to a different board that fits your topic of discussion a bit better. This means you’ll get better engagement on your post, and it keeps our Community organized so users can more easily find information.

As you’ll notice, your Topic is now in the Project Development Help and Advice board. No action is needed on your part; you can continue the conversation as normal here.

Additionally, the Community Forum is a great place to ask other GitHub users to help you problem solve, but we do recommend only posting small pieces of code or other details that help clarify your question, and then linking to a repository or other resource for your project for more in-depth information. Posts like this can be overwhelming and become too long, which might actually result in a longer wait for help from other users. 

Thanks again for being here. Cheers!