Test, tst, un, uninstall, unpublish, unstar, up, update, v, Search, set, shrinkwrap, star, stars, start, stop, t, team, Rebuild, repo, restart, root, run, run-script, s, se, Outdated, owner, pack, ping, prefix, prune, publish, rb, Install-test, it, link, list, ln, login, logout, ls, Nvm really just needs one key=value from itĪnd the main time is actually not even wasted by reading, but by npms horrific startup time it self, which could be greatly resolved by just lazy loading stuff.īut, hey that are just words, the following timing of just getting the help dialogue says everything:Īccess, adduser, bin, bugs, c, cache, completion, config,ĭdp, dedupe, deprecate, dist-tag, docs, doctor, edit,Įxplore, get, help, help-search, i, init, install, simple file format (even less than ini is capable of).Given the following circumstances: npmrc is easy to find and to parseĪs we can get from this document, npm has Why was npm config get prefix was used after all?.Which impact have runtime changes to this prefix? I.e.Why exactly does nvm needs to check for the prefix being set or not?. Hey just want to get a small discussion going, and probably an attempt to get nvm really fast:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |