Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/npm/cli.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/bin
AgeCommit message (Collapse)Author
2015-10-22src: Update formatting to be compatible with standard@5Sebastiaan Deckers
PR-URL: https://github.com/npm/npm/pull/9954
2015-08-21windows: search for a user-installed npmJoão Reis
This changes npm.cmd and the npm script when running in Cygwin to look for an npm installation in prefix, running it if found. The default npm is used to get the prefix. This implements the changes described in https://github.com/joyent/node/issues/8528 . Fixes joyent/node#8528. Reference: joyent/node#8554. Fixes: #6412 PR-URL: https://github.com/npm/npm/pull/9089
2015-07-25config: Add option to turn off progress barsRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9037 Fixes: https://github.com/npm/npm/issues/8704
2015-06-26src: make the npm source comply with `standard`Forrest L Norvell
This is a huge set of mostly mechanical changes. Going forward, all changes to the npm source base are expected to comply with `standard`, and it's been integrated into the test suite to enforce that. There are a few notes below about specific classes of changes that need to be handled specially for npm's code base. standard: "Expected error to be handled." `standard` only expects errors spelled "err" to be handled. `npm-registry-mock` never actually invokes its callback with an error, so in some cases I just changed it to be spelled "er" and called it good. standard: "Expected a "break" statement before 'case'." This behavior is actually on purpose, and I don't feel like rewriting the affected code right now (or, you know, ever). So I added code comments disabling the checks in the three applicable changes. standard: "x is a function." Rebinding functions created via declarations (as opposed to expressions) is a no-no? PR-URL: https://github.com/npm/npm/pull/8668
2015-06-26Stop stray progressbars from appearing when logging is used in non-progress ↵Rebecca Turner
commands
2015-06-26Swap the spinner out for the new progress bar code in npmlogRebecca Turner
2015-05-22windows: run node-gyp.js instead of opening itbangbang93
PR-URL: https://github.com/npm/npm/pull/8324
2015-02-27node-gyp: enable overriding node-gyp binaryAlain Kalker
Enable overriding the node-gyp binary used by npm by specifying a config option, similar to specifying the python interpreter. Example usage: npm install --node-gyp=<path-to-custom-node-gyp>
2014-10-16defactored npmconf back into npmForrest L Norvell
2014-09-13style tweaks & dead variable removalForrest L Norvell
2014-09-12Remove enginesisaacs
Node v0.6 is pretty much gone at this point. Also, the -pre upsets SemVer 4, making it annoying to test npm on Node in development.
2014-05-13fix cygwin encoding issueKarsten Tinnefeld
make sure that npm script runs on cygwin platform even when installed in DOS encoding cf. http://sourceware.org/ml/cygwin-announce/2009-07/msg00002.html (option 4a)
2012-08-15Use new npmconf moduleisaacs
2012-08-13Show all versions in 'npm version<noargs>'isaacs
2012-06-17Fix #2465: Make npm script and windows shims cygwin-awarePhillip Howell
2012-06-11Use read-package-json depisaacs
2012-06-07Replace the log util with npmlog moduleisaacs
This feels so good. lib/utils/log.js is the worst kind of glue code that keeps the npm project from being properly abstracted into independent pieces. In the process, also cleaned up a lot of unproductive logging, and made the npm-debug.log generated on errors be a bit more easy to read.
2012-03-27Abstract out 'uid-number' to a separate dependencyisaacs
2012-03-13Always favor the bundled node-gypisaacs
2012-02-23Add --versions flag to show the version of node as wellisaacs
For @mcavage
2012-02-16Simplify confusing windows pathsisaacs
2012-01-13Remove npm-g/npm_g bin namesisaacs
Unnecessary and unportable
2012-01-13git bash shim for npm itselfisaacs
2011-12-06move process.title to correct spotisaacs
2011-11-17npm cmd files, for easier node msi buildingisaacs
2011-10-15Avoid accidentally opening npm.js with WSHisaacs
2011-10-10Fix #1521 Remove unnecessary shebangsisaacs
2011-09-26Merge remote branch 'deanlandolt/winbin' into winbinisaacs
Conflicts: lib/utils/mkdir-p.js lib/utils/output.js
2011-09-17Add shebangs for bin/ scripts, chmod 755 for completion.shOleg Efimov
2011-09-15Minor cli.js styleisaacs
2011-09-07make command proxy silentDean Landolt
2011-09-07relativize npm batch script using %~dp0Dean Landolt
2011-09-07use cmd instead of bat extension, see: ↵Dean Landolt
http://stackoverflow.com/questions/148968/windows-batch-files-bat-vs-cmd
2011-09-04batch file for running on Windowsisaacs
2011-08-07Use rimraf instead of local thingisaacs
2011-07-20s/sys/util/g finallyisaacs
2011-07-20Abstract out graceful-fsisaacs
2011-06-11Support 'npm-g' as a global binisaacs
2011-04-30Read contributors out of AUTHORS file, if presentisaacs
2011-03-30Rename optparse to noptisaacs
2011-03-25Use optparse instead of parse-args.jsisaacs
Also, move default-config.js and the optparse hashes into config-defs.js
2011-02-19chmodisaacs
2011-02-12Closes GH-547 Split semver into a separate utilityisaacs
2011-02-08Report the error, rather than just failing badly.isaacs
2011-02-08Numeric UID/GID values, and remove the script runnerisaacs
Since node can run scripts as a uid/gid anyway, the script runner is unnecessary. Numberizing the uid and gid make them suitable as arguments to chown.
2011-02-08make the uid numeric, and log a bit moreisaacs
2011-02-08A script to get the numeric uid/gidisaacs
2011-02-08Specify uid and gid to script runnerisaacs
2011-02-08Broken first pass at setuid script runnerisaacs
2011-01-09Use the package.json data in the installationisaacs
So to verify the version of node in use. Note that this install.sh can't be deployed until AFTER this node is published.