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/lib
AgeCommit message (Collapse)Author
2015-10-23deps: When we replace/upgrade a dep, remove all its deps tooRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9929
2015-10-23deps: Move adding of modules to sets of modules into a functionRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9929
2015-10-23deps: Move adding to a set of module names to a functionRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9929
2015-10-23deps: Refactor module matchers into stand alone functionsRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9929
2015-10-22fetch-package-metadata: close, what, I don't evenRebecca Turner
2015-10-22save: If a shrinkwrap already has dev deps, make sure they're keptRebecca Turner
When running `install --save` in a folder with a shrinkwrap that has dev-only dependencies in it, it's important that we don't then throw away the dev dependencies just because they didn't say `install --save --also=dev`. PR-URL: https://github.com/npm/npm/pull/9992 Fixes: #9647
2015-10-22error-handler: Encourage users to update node & npm before contacting ↵Forbes Lindesay
package maintainers PR-URL: https://github.com/npm/npm/pull/9950
2015-10-22src: Update formatting to be compatible with standard@5Sebastiaan Deckers
PR-URL: https://github.com/npm/npm/pull/9954
2015-10-16errors: Show available versions as lists instead of JSONRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9927
2015-10-16deps: mark our installable flag as internalRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9928
2015-10-12Revert "lifecycle: Swap out custom logic with add-to-path module"Rebecca Turner
This reverts commit 22a3af055f934f8de20ebd5f4a286447dda84f81.
2015-10-09shrinkwrap: do not fail on optional dependenciesMaximilian Antoni
If an optional dependency was not installed, shrinkwrap fails with a message saying that a required dependency is missing. This patch checks whether a missing dependency was listed in the optionalDependencies. PR-URL: https://github.com/npm/npm/pull/9879
2015-10-09install: Update --only option to install only the argument env regardless of ↵Daijiro Wachi
the NODE_ENV. The following is the condition of setting the value of the development / production option. npm install + dev: true + prod: true --only=dev + dev: true + prod: false --only=prod || NODE_ENV=production + dev: false + prod: true PR-URL: https://github.com/npm/npm/pull/9835 Fixes: #9463
2015-10-09deps: Treat lack of requirement name as failure to find itThomas Michael McTiernan
Fixes #9669 PR-URL: https://github.com/npm/npm/pull/9715
2015-10-09lifecycle: Swap out custom logic with add-to-path moduleKent C. Dodds
PR-URL: https://github.com/npm/npm/pull/9553
2015-10-09child-path: Compute the path of a new child module in only one placeRebecca Turner
PR-URL: //github.com/npm/npm/pull/9890 Fixes: #9766
2015-10-09package-id: Use getPackageId more consistently in diagnosticsRebecca Turner
PR-URL: //github.com/npm/npm/pull/9890 Fixes: #9766
2015-10-09package-id: rename into utils, from install/get-package-idRebecca Turner
PR-URL: //github.com/npm/npm/pull/9890 Fixes: #9766
2015-10-09module-name: Factor out module name readingRebecca Turner
Bring consistent guarding against null/undefined and consistent business logic. PR-URL: //github.com/npm/npm/pull/9890 Fixes: #9766
2015-10-09actions,diff-trees: rebuild bundles via npm3 mechanismsRebecca Turner
Previously this was being done implicitly via `build.linkStuff`– we're now avoiding that. PR-URL: https://github.com/npm/npm/pull/9891 Fixes: #9643 Fixes: #9664
2015-10-09lifecycle: Remove dead code around npm.ROLLBACK globalRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9892
2015-10-01install: Switch from clone to a tree-copier that's aware of our datastructuresRebecca Turner
Lodash's deep-clone is being updated to not have the catostrophic scalaing issues it had when this patch was written, but even still, using something tailor-made will necessarily be faster. PR-URL: https://github.com/npm/npm/pull/9803 Fixes: #8826
2015-10-01logical-tree: Make it mutate to improve performanceRebecca Turner
The clone we were doing to save ourselves from mutation proved to be excessively slow. While lodash is being updated to not have the same scaling issues, it was determined that we weren't gaining anything from not mutating here, so there was no reason to pay even a lesser price. PR-URL: https://github.com/npm/npm/pull/9803 Fixes: #8826
2015-09-25cache: also update port when updating protocolJames Hartig
PR-URL: https://github.com/npm/npm/pull/9471
2015-09-25pack: Don't bother reading the tree if nothing is bundledRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9667
2015-09-25pack: Pass in our tree object via closures instead of propertiesRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9667
2015-09-25validate-tree: When normalize-package-data throws, capture that as a warningRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9741
2015-09-25get-package-id: Don't infer package names outside of UXRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9744 Fixes: #9695
2015-09-18ls: install: Stop warning about cruft in module directoriesRebecca Turner
2015-09-18install/deps: Report error gracefully with invalid URL format dependencies=
2015-09-11adduser: remove obsolescent process.binding useForrest L Norvell
Fixes: #9544 PR-URL: https://github.com/npm/npm/pull/9549
2015-09-10link: allow npm link to run on windows with prerelease versions of nodeJon Hall
(provided they are newer than 0.7.9) PR-URL: https://github.com/npm/npm/pull/9506 Fixes: #9505
2015-09-10gently-rm: Treat cmd-shims the same way we treat symlinksRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9537 Fixes: 9394
2015-08-28error-handler: improve EISDIR error messageKenan Yildirim
Reports of `EISDIR` on the issue tracker are almost exclusively caused by users trying to install something that does not have a `package.json`. However, it is clearly difficult for many users to discern this simple problem from the error code alone. So let's expand upon it. PR-URL: https://github.com/npm/npm/pull/9396
2015-08-28install: don't warn on preferGlobal for devDepsMarcin Cieslak
Followup-To: https://github.com/npm/npm/issues/1648 Fixes: https://github.com/npm/npm/issues/8517 PR-URL: https://github.com/npm/npm/pull/9409 PR-URL: https://github.com/npm/npm/pull/8841
2015-08-28install: warn on preferGlobal when there's no depsKat Marchán
PR-URL: https://github.com/npm/npm/pull/9409
2015-08-27fetch-package-metadata: Add direct support for local modulesRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9369 Fixes: #9308
2015-08-27deps: Use package relative paths for specifier realizationRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9367 Fixes: #9205
2015-08-26lifecycle: Add additional loggingMarcin Cieslak
To make debugging of lifecycle scripts easier PR-URL: https://github.com/npm/npm/pull/9227
2015-08-21diff-trees: Make install order more consistent for directly dependenciesRebecca Turner
The install order is determined by: 1) The location of the thing to be installed relative to the root module. 2) Dependency order, such that a -> b -> c will install modules as: c, b, a 1 is deterministic, regardless of what's being installed. But 2 can change the order of things higher in the dep tree. Eg, b, or a might get sorted earlier if c requires them. This mostly doesn't matter, but it does mean that if you have two modules with conflicting bins, they _can_ get installed in different orders. This changes sorts all of the top level modules to be LAST, in location order (1), and then sorts all the rest per (2). This ensures that top level modules have a deterministic install order. (Non top level modules can't have bin conflicts as that's treated the same as a version conflict and the conflicting module would be hoisted.) PR-URL: https://github.com/npm/npm/pull/9274 Fixes: #8995
2015-08-21logical-tree: Make sure user installed modules are attached to root of ↵Rebecca Turner
logical tree PR-URL: https://github.com/npm/npm/pull/9344 Fixes: #9113
2015-08-21update: Fix path used to run the install relative toRebecca Turner
Previously I was using the path of the module to be updated. But no, silly, we want the path that CONTAINS it. PR-URL: https://github.com/npm/npm/pull/9303 Fixes: #9095
2015-08-21ls: Elminate warnings about missing package.json at top levelRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9343 Fixes: #9113
2015-08-21test: Fix the progress-config test when run from travis or other CIRebecca Turner
We have special code to disable the progress bar on travis (and other CI) to save ourselves and our users a lot of unhelpful output. Unfortunately as this test didn't take that into account, it immediately exploded in this envs. So we fix that up, PLUS we add tests for the various env options for suppressing progress bars. PR-URL: https://github.com/npm/npm/pull/9304
2015-08-21lifecycle: add /d and /s to cmd.exeMarcin Cieslak
/d disables cmd.exe AutoRuns feature, where registry entry points to the script that will be executed when cmd.exe starts. Surprisingly a lot of users hase "CD \" or similar command there which causes lifecycle scripts to fail, since relative path to the script no longer works (and package.json has no way to deduce absolute path) /s enables handling of quotes, so that you can have "C:\Program Files\Node\node.exe" quoted in your script. Node's child_process.exec() is doing the same. We prevent additional quoting by libuv already by setting uv_spawn() flag UV_PROCESS_WINDOWS_VERBATIM_ARGUMENTS. If those flags are not set there is no way package.json can reliably tell us to run "node" executable with a relative script path: "scripts": { "install": "node scripts/install.js" } Without /d "node" invocation may end up in a random directory as a result of the AutoRuns command. Fixes: #8751 Fixes: #7333 PR-URL: https://github.com/npm/npm/pull/9245
2015-08-21lifecycle: keep private values out of child procsForrest L Norvell
npm@1.x didn't include configuration values prefixed with an underscore in the environment passed to chiled processes. npm@2.x includes the notion of scoped configuration, where a nerfed URL can be used to prefix configuration, some of which might be underscore-prefixed without the scope. Add that behavior to npm@2 and close this regression. PR-URL: https://github.com/npm/npm/pull/9348
2015-08-14access: updated to support teams and orgs featuresKat Marchán
PR-URL: https://github.com/npm/npm/pull/9011
2015-08-14whoami: make needauth err more genericKat Marchán
PR-URL: https://github.com/npm/npm/pull/9011
2015-08-14team: initial implementation of team commandKat Marchán
PR-URL: https://github.com/npm/npm/pull/9011
2015-08-14unbuild: Tell gently-rm about which modules we are removing bins forRebecca Turner
PR-URL: https://github.com/npm/npm/pull/9198
generated by cgit v1.2.3 (git 2.25.1) at 2024-08-22 17:35:13 +0300