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/doc
AgeCommit message (Collapse)Author
2017-02-10doc: document new auth optionsKat Marchán
PR-URL: https://github.com/npm/npm/pull/13389 Credit: @zkat Reviewed-By: @iarna
2017-01-25doc: Fix typo and replace http with https (#15539)Daijirō Wachi
* doc: fix typo in lib/fetch-package-metadata.md * doc: replace http://opensource.org with https in doc/files/package.json.md PR-URL: https://github.com/npm/npm/pull/15539 Credit: @watilde Reviewed-By: @iarna
2017-01-25doc: add section about scopes only belonging to user/org (#15520)Henry Zhu
PR-URL: https://github.com/npm/npm/pull/15520 Fixes: https://github.com/npm/docs/issues/795 Credit: @hzoo Reviewed-By: @iarna
2017-01-25doc: clarify that unscoped packages can depend on scoped packages (#15480)chocolateboy
as per the discussion in [1], clarify the fact that unscoped packages can depend on scoped packages (and *vice versa*), contrary to the initial proposal and announcements. also: - s/un-scoped/unscoped/ as per e.g. [2] - fix typos + minor cosmetic tweaks [1] https://github.com/npm/npm/issues/15305#issuecomment-272599537 [2] https://github.com/npm/npm/blob/v4.1.1/doc/cli/npm-access.md PR-URL: https://github.com/npm/npm/pull/15480 Credit: @chocolateboy Reviewed-By: @iarna
2017-01-25doc: documented new searchlimit optionKat Marchán
PR-URL: https://github.com/npm/npm/pull/15481 Credit: @zkat Reviewed-By: @iarna Reviewed-By: @bcoe
2017-01-25npm: Put the npm-debug logs in the cache folder, not cwd.isaacs
We also are storing a configurable number of previous log files. PR-URL: https://github.com/npm/npm/pull/11439 Fixes: #5252 Fixes: #6350 Fixes: #1548 Fixes: #7614 Credit: @KenanY Credit: @othiym23 Credit: @isaacs Credit: @iarna
2016-12-16doc: rewrite npm doctor docsForrest L Norvell
PR-URL: https://github.com/npm/npm/pull/15235 Credit: @othiym23 Reviewed-By: @iarna
2016-12-15doctor: add new subcommandDaijiro Wachi
This command will diagnose user's environment and let the user know some recommended solutions if they potentially have any problems related to npm. Credit: @watilde Reviewed-By: @othiym23 Reviewed-By: @iarna PR-URL: https://github.com/npm/npm/pull/14582 Fixes: #6756
2016-12-13doc: Update `npm cache` docs to use more consistent languageJonah Moses
PR_URL: https://github.com/npm/npm/pull/15157 Credit: @JonahMoses Reviewed-By: @watilde Reviewed-By: @iarna
2016-12-13metrics: Record and report success metricsRebecca Turner
Fixes: #12529 Credit: @iarna Reviewed-By: @othiym23
2016-11-18doc: we do NOT check npmrc permissionsRebecca Turner
PR-URL: https://github.com/npm/npm/pull/14559 Credit: @iarna Reviewed-By: @othiym23
2016-11-18doc: Add a note about uppercase env varsVille Lahdenvuo
Credit: @tuhoojabotti Reviewed-By: @iarna PR-URL: https://github.com/npm/npm/pull/14546
2016-11-18doc: Document `sign-git-tag` in npm-version(1)'s 'configuration' sectionAlex Jordan
Credit: @strugee Reviewed-By: @iarna PR-URL: https://github.com/npm/npm/pull/14472
2016-11-18doc: Sync up the dispute policy with the one on npmjs.comMike Engel
The dispute policy at https://www.npmjs.com/policies/disputes is the current version of the dispute policy. This syncs up the dispute policy document here to match what's on the site. Fixes: #13302 PR-URL: https://github.com/npm/npm/pull/14406 Credit: @mike-engel Reviewed-By: @iarna
2016-11-15doc: update the GitHub URL examplesDouglas Wilson
This updates the two GitHub URL examples that used to be projects under the `visionmedia` organization and uses the current URLs for those projects. PR-URL: https://github.com/npm/npm/pull/14609 Credit: @dougwilson Reviewed-By: @iarna
2016-11-04doc: Document new shrinkwrap dev dep behaviorRebecca Turner
Fixes: #14479 Credit: @iarna PR-URL: https://github.com/npm/npm/pull/14519 Reviewed-By: @othiym23
2016-11-03doc: add a little note about ENOSELF in install.mdKat Marchán
PR-URL: https://github.com/npm/npm/pull/14501 Credit: @zkat Reviewed-By: @othiym23
2016-10-25doc: Add note on when `prepare` script is runSimen Bekkhus
Credit: @SimenB PR-URL: https://github.com/npm/npm/pull/14380 Reviewed-By: @zkat
2016-10-20doc: Document headers we add to registry requestsRebecca Turner
Credit: @iarna PR-URL: https://github.com/npm/npm/pull/14129 Reviewed-By: @ashleygwilliams
2016-10-20npm: Send Npm-Scope header along with requests to registryRebecca Turner
Npm-Scope is set to the scope of the current top level project. Credit: @iarna PR-URL: https://github.com/npm/npm/pull/14129 Reviewed-By: @othiym23
2016-10-20tag: Remove deprecated tag commandRebecca Turner
Folks should be using the `dist-tag` command now. Fixes: #6274 PR-URL: https://github.com/npm/npm/pull/14328 Credit: @iarna Reviewed-By: @zkat
2016-10-20doc: replace prepublish with prepare in package.json docsKat Marchán
PR-URL: https://github.com/npm/npm/pull/14290 Credit: @zkat Reviewed-By: @othiym23
2016-10-20doc: document prepublish-on-install deprecationForrest L Norvell
Now all we have to remember to do is come back to this when we put out `npm@5`. PR-URL: https://github.com/npm/npm/pull/14290 Credit: @othiym23 Reviewed-By: @watilde Reviewed-By: @iarna Reviewed-By: @zkat
2016-10-19npat: Remove the npat featureRebecca Turner
PR-URL: https://github.com/npm/npm/pull/14329 Credit: @iarna Reviewed-By: @zkat
2016-10-19run-script: change default for `--scripts-prepend-node-path` to `warn-only`Anna Henningsen
Change the default behaviour of npm to never prepending the current node executable’s directory to `PATH` but printing a warning in the cases in which it previously did. PR-URL: https://github.com/npm/npm/pull/13409 Credit: @addaleax Reviewed-By: @zkat Reviewed-By: @othiym23
2016-10-19run-script: Add option to ignore the current node executable for PATHAnna Henningsen
Add a `--scripts-prepend-node-path` option that controls `npm`’s behaviour with respect to adding the directory of the current `node` executable to the `PATH`, even if that means that `npm` will invoke a different `node` executable than the one which it is running. This is a non-invasive solution to some of the problems described in https://github.com/npm/npm/issues/12318. It should not come with any drawbacks for npm’s side, as it shifts the responsibility of making sure that the `PATH` variable contains everything it should to whoever invoked npm with `--scripts-prepend-node-path=false`. While https://github.com/npm/npm/pull/12968 may have addressed some of the problems described there, it does not help in the case that the `PATH` has explicitly been overridden with the intention of having a different `node` executed. [squash] test: anticipate coverage tooling possibly setting --scripts-prepend-node-path As one of the motivations for introducing `--scripts-prepend-node-path` is that `spawn-wrap` (which npm itself uses for coverage) can make use of that option, anticipate that change in order to not break the test suite when updating that dependency at a later point. [squash] tests for scripts-prepend-node-path=auto [squash] implement `warn-only` setting for `--scripts-prepend-node-path` Adds a setting that is basically equivalent to `--scripts-prepend-node-path=false` but emits a warning informing the user about the existence of the option in the cases in which `npm` currently modifies `PATH`, as sometimes that’s in the user’s interest. [squash] fixup tests for windows PR-URL: https://github.com/npm/npm/pull/13409 Credit: @addaleax Reviewed-By: @zkat Reviewed-By: @othiym23
2016-10-13doc: updated docs for search optionsKat Marchán
Credit: @zkat PR-URL: https://github.com/npm/npm/pull/13746 Reviewed-By: @othiym23
2016-10-07doc: Update package.json example to include github branchesSteven
Credit: @stevokk Reviewed-By: @iarna PR-URL: https://github.com/npm/npm/pull/13904
2016-09-09doc: clarify how config files are configuredForrest L Norvell
PR-URL: https://github.com/npm/npm/pull/13911 Credit: @othiym23 Reviewed-By: @zkat
2016-09-09doc: update semver docs for semver@5.3.0Kat Marchán
Credit: @zkat
2016-09-09doc: per-user config file isn't hardcodedJason Karns
Document that the per-user config file respects the `$NPM_CONFIG_USERCONFIG` env var, defaulting to ~/.npmrc PR-URL: https://github.com/npm/npm/pull/13493 Credit: @jasonkarns Reviewed-By: @iarna
2016-09-09shrinkwrap: save-dev updates shrinkwrap fileSzymon Nowak
Running 'npm install --save-dev' will update shrinkwrap file, but only if there already are any dev dependencies in this file. Fixes: #11735 PR-URL: https://github.com/npm/npm/pull/13860 Credit: @szimek Reviewed-By: @iarna
2016-09-09doc: explain how to set node env in bin scriptsMax
Fixes: #12438 Credit: @mxstbr Reviewed-By: @zkat PR-URL: https://github.com/npm/npm/pull/13598
2016-09-09doc: add details about npmrc commentsMichael Jasper
I found that information about commenting lines in a `.npmrc` file was lacking from the official documentation. I've updated the doc to reflect currently supported ways to commenting lines in the npm config file as found through reading other sources and through experimentation with different ways of adding comments. PR-URL: https://github.com/npm/npm/pull/13655 Credit: @mdjasper Reviewed-By: @zkat
2016-09-09doc: Minor grammar fix in docs for npm scriptsAndrew Meyer
PR-URL: https://github.com/npm/npm/pull/13682 Credit: @Ajedi32 Reviewed-By: @zkat
2016-09-09doc: npm link will link bin of project.legodude17
This documents the fact that `npm link` will link the files specified in the `bin` field of `package.json` to `{prefix}/bin/{name}`. PR-URL: https://github.com/npm/npm/pull/13717 Credit: @legodude17 Reviewed-By: @zkat
2016-09-09tar: ignore *.orig filesChristopher Hiller
Credit: @boneskull PR-URL: https://github.com/npm/npm/pull/13708 Reviewed-By: @zkat
2016-08-12doc: Clarify that npm@2 is required for scoped packagesDaniel Paz-Soldan
PR-URL: https://github.com/npm/npm/pull/10167 Credit: @danpaz Reviewed-By: @othiym23
2016-08-12doc: explain difference between `version` and `preversion` scriptsChristophe Hurpeau
PR-URL: https://github.com/npm/npm/pull/13349 Credit: @christophehurpeau ReviewedBy: @iarna
2016-08-11install: add GIT_EXEC_PATH to git env whitelistMichael Hart
Fixes: #13353 PR-URL: https://github.com/npm/npm/pull/13358 Credit: @mhart Reviewed-By: @othiym23
2016-07-07run-script: only prepend node dir to PATH if not already in PATHSergey Simonchik
Fixes: #12318 PR-URL: https://github.com/npm/npm/pull/12968 Credit: @segrey Reviewed-By: @iarna
2016-07-01doc: correct link to `npm-tag` from tag docsSimon MacDonald
User @SimenB found a broken link. I think that the `npm-tag(3)` should actually be `npm-dist-tag(1)` in the see also section to link to the non-deprecated command. Fixes: https://github.com/npm/npm/issues/13113 Credit: @macdonst PR-URL: https://github.com/npm/npm/pull/13189 Reviewed-By: @zkat
2016-06-24doc: Remove extra backtick from npm-ls docsAleksey Shvayka
Credit: @shvaikalesh PR-URL: https://github.com/npm/npm/pull/13127 Reviewed-By: @iarna
2016-06-24doc: npm-publish(1) mentions npm-pack(1)Han Seoul-Oh
Credit: @laughinghan Reviewed-By: @iarna PR-URL: https://github.com/npm/npm/pull/13080
2016-06-17doc: Describe how to run lifecycle scripts of dependencies.Tapani Moilanen
Prior to npm version 2, you could do this with `npm run <packagename> <scriptname>`. These days, npm run can pass arguments through to the script instead. Related to the removal of the earlier possibility of running these scripts with npm run <pkg> <script> (removed from this doc in [npm/npm@70a3ae4](https://github.com/npm/npm/commit/70a3ae4d4ec76b3ec51f00bf5261f1147829f9fe)). Workaround mentioned in [npm/npm#9186](https://github.com/npm/npm/issues/9186). Ref [npm/docs#704](https://github.com/npm/docs/issues/704). PR-URL: https://github.com/npm/npm/pull/12983 Credit: @Tapppi
2016-06-16shrinkwrap: Add new "shrinkwrap" lifecycle scriptSimen Bekkhus
Fixes: #10744 Credit: @SimenB PR-URL: https://github.com/npm/npm/pull/12814
2016-06-16npm: Only enable progressbar if we have a ttyRebecca Turner
With the older version of gauge (and thus the older version of npmlog), if you didn't have a tty then `gauge.enable` was ignored. This is no longer the case, so now we need to do tty detection before enabling it ourselves. As a bonus, this now means tty detection is done exactly the same way for the progress bar as it is for color. PR-URL: https://github.com/npm/npm/pull/13075 Credit: @iarna
2016-06-03doc: add config.gypi to package.json docsDmitry Kirilyuk
PR-URL: https://github.com/npm/npm/pull/12933 Credit: @Jokero Reviewed-By: @zkat
2016-05-27doc: small grammar fix in cli/npm.mdAndré Herculano
Reviewed-By: @zkat Credit: @andresilveira PR-URL: https://github.com/npm/npm/pull/12802
2016-05-27doc: Add `NOTICE` to files included in packSimen Bekkhus
`NOTICE` files started getting included after https://github.com/npm/fstream-npm/pull/17. This documents that. Reviewed-By: @zkat Credit: @SimenB PR-URL: https://github.com/npm/npm/pull/12782
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-13 08:02:10 +0300