Age | Commit message (Collapse) | Author |
|
- chore(docs): remove html from docs build
- feat(docs): migrate new Gatsby site to cli/docs
- chore(docs): fix docs url path
- chore(docs): add new build doc step
- chore(docs): add static linking
- chore(docs): add npm favicon
- chore(docs): update files for tests
- chore(docs): make relative paths absolute
- chore(docs): fix routing on docs dependant tests
- chore(docs): add prepublishOnly docs building step
- chore(docs): add docs/public to .gitignore
- chore(docs): rename dot json markdown files with hyphen names
- chore(docs): clean package.json
- chore(docs): highlight scripts in list
- chore(docs): add strong styles
- chore(docs): fix .json links on markdown
- Added copy to the features page
- Added an install page (copied from existing online docs)
- Added a FeatureLink component to components/links.js
- feat(docs): replace docs sh script with node
- chore(docs): fix docs building process
- chore(docs): docs folder cleanup
PR-URL: https://github.com/npm/cli/pull/274
Credit: @claudiahdz
Close: #274
Reviewed-by: @ruyadorno
|
|
Adds a new config `--format-package-lock`, which defaults to true.
If set to false, then the package lock will be written without any
indentation or line breaks.
PR-URL: https://github.com/npm/cli/pull/248
Credit: @bl00mber
Close: #248
Reviewed-by: @isaacs
Note: squashed and edited slightly for style. -- @isaacs
|
|
docs(package-lock): Added package-lock resolved ex
Added a concrete example on how the url from the resolved field of a
package-lock.json file will be used along with the configured registry
value in order to build the URL for that package.
|
|
|
|
Just replaced Integer.MAX_SAFE_INTEGER with Number.MAX_SAFE_INTEGER.
PR-URL: https://github.com/npm/cli/pull/229
Credit: @gall0ws
Close: #229
Reviewed-by: @isaacs
|
|
|
|
I spent a couple hours debugging the fact that package names in that key aren't supposed to include their versions! Assumed that it would need to have the same syntax as when running `npm install`. Thought this would be a good contribution for future readers.
|
|
implementation added in #31
|
|
PR-URL: https://github.com/npm/cli/pull/90
Credit: @zkat
Reviewed-By: @aeschright
Reviewed-By: @iarna
|
|
PR-URL: https://github.com/npm/cli/pull/135
Credit: @emilis-tm
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/cli/pull/160
Credit: @ahasall
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/cli/pull/140
Credit: @greysteil
Reviewed-By: @aeschright
|
|
|
|
PR-URL: https://github.com/npm/cli/pull/116
Fixes: https://npm.community/t/4054
Credit: @larsgw
Reviewed-By: @aeschright
|
|
|
|
|
|
I keep typing `npm dist-tags` expecting it to print out a list of
dist-tags and instead it yells at me and that feels very un-npm-y.
PR-URL: https://github.com/npm/cli/pull/106
Credit: @isaacs
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/cli/pull/71
Credit: @GeorgeTaveras1231
Reviewed-By: @zkat
|
|
|
|
PR-URL: https://github.com/npm/cli/pull/68
Credit: @neverett
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/cli/pull/96
Credit: @midare
Reviewed-By: @zkat
|
|
publish (#83)
Not sure when `--dry-run` was introduced, I assume it was introduced in npm 6 (correct me if I'm wrong). Anyway, hopefully this will prevent future developers from making the mistake of using it in npm 5 (like I did).
PR-URL: https://github.com/npm/cli/pull/83
Credit: @kjin
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/cli/pull/82
Credit: @seishun
Reviewed-By: @zkat
|
|
* feat(cli, outdated): Adds 'Homepage' to outdated --long output.
- `package.json`'s `homepage` property is displayed when using the `--long` option for `npm outdated`
* test: npm outdated --long
- Adds `homepage` to `--parseable` output.
- Updates `npm outdated --long` test to include `homepage` in expected output.
- Adds `homepage` to `npm-outdated` documentation.
* fix: javascript standard style updates
PR-URL: https://github.com/npm/cli/pull/81
Credit: @jbottigliero
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/cli/pull/78
Credit: @hugovk
Reviewed-By: @zkat
|
|
* edit: fix handling of scoped packages
* edit: fix usage info
* docs: fix docs for the npm-edit command
PR-URL: https://github.com/npm/cli/pull/75
Credit: @larsgw
Reviewed-By: @iarna
|
|
See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432
TL;DR:
> To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above.
Ref: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432
PR-URL: https://github.com/npm/cli/pull/74
Credit: @scotttrinh
Reviewed-By: @iarna
Reviewed-By: @zkat
|
|
I found this page useful for setting up npm command completion. Thank you npm
documentation team.
This suggested changed is based on my system which runs Ubuntu where
the completion directory path for bash is found in
/etc/bash_completion.d and not /usr/local/etc/bash_completion.d
I dug around docs for this in The Bash Manual
https://www.gnu.org/software/bash/manual/bashref.html#Programmable-Completion
and on some an old (sadly retired) Debian Admin Site
https://debian-administration.org/article/317/An_introduction_to_bash_completion_part_2
which seemed supportive of the dir being in /etc but I do not have access
to an OS X machine where I guess bash_completion.d could be in /usr/local/etc
so I left it in.
PR-URL: https://github.com/npm/cli/pull/72
Credit: @RobertKielty
Reviewed-By: @zkat
|
|
With some tests I note npm use default branch of repository instead of `master`.
PR-URL: https://github.com/npm/cli/pull/64
Credit: @zckrs
Reviewed-By: @zkat
|
|
Credit: @zkat
Reviewed-By: @jefflembeck
|
|
PR-URL: https://github.com/npm/cli/pull/48
Credit: @neverett
Reviewed-By: @zkat
|
|
Fixes: https://npm.community/t/1327
PR-URL: https://github.com/npm/cli/pull/46
Credit: @SneakyFish5
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/cli/pull/41
Credit: @reconbot
Reviewed-By: @zkat
|
|
* doc: Mention terms of use in npm-registry
* doc: Mention registry terms of use in manpage
* doc: Update terms of use language in README
Credit: @kemitchell
PR-URL: https://github.com/npm/cli/pull/54
|
|
added a header for usage with process.env to separate section from 'current lifecycle event' and make it easier to find
PR-URL: https://github.com/npm/cli/pull/14
Credit: @mwarger
Reviewed-By: @zkat
|
|
`npm audit` currently exits with exit code 1 if any vulnerabilities are found of any level.
Add a flag of `--audit-level` to `npm audit` to allow it to pass if only vulnerabilities below a certain level are found.
Example: `npm audit --audit-level=high` will exit with 0 if only low or moderate level vulns are detected.
Fixes: https://npm.community/t/245
PR-URL: https://github.com/npm/cli/pull/31
Credit: @lennym
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/cli/pull/36
Credit: @noahbenham
Reviewed-By: @zkat
|
|
Remove publish from list of commands not affected by dry-run
PR-URL: https://github.com/npm/cli/pull/34
Credit: @joebowbeer
Reviewed-By: @zkat
|
|
|
|
PR-URL: https://github.com/npm/cli/pull/7
Credit: @XhmikosR
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/cli/pull/26
Credit: @dwilches
Reviewed-By: @zkat
|
|
+ specifer => specifiers
+ relavent => relevant
+ properities => properties
PR-URL: https://github.com/npm/cli/pull/16
Credit: @watilde
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/cli/pull/15
Credit: @Mstrodl
Reviewed-By: @zkat
|
|
|
|
PR-URL: https://github.com/npm/npm/pull/12697
Credit: @tribou
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/npm/pull/20554
Credit: @luislobo
Reviewed-By: @zkat
Reviewed-By: @iarna
|
|
Explicitly state that republishing an unpublished package requires a 72h waiting period.
PR-URL: https://github.com/npm/npm/pull/20920
Credit: @gmattie
Reviewed-By: @zkat
|
|
npm install foo, not npm install foo``
PR-URL: https://github.com/npm/npm/pull/21165
Credit: @hchiam
Reviewed-By: @zkat
|
|
PR-URL: https://github.com/npm/npm/pull/21064
Credit: @roblourens
Reviewed-By: @zkat
|
|
I wasn't clear on the exact behaviour with the shorthand, but I think this change is correct.
PR-URL: https://github.com/npm/npm/pull/21019
Credit: @davidgilbertson
Reviewed-By: @zkat
|