node_modules/npm/CHANGELOG.md

39 * [`36e6c01d3`](https://github.com/npm/cli/commit/36e6c01d334c4db75018bc6a4a0bef726fd41ce4) git tag…
136 …le/commit/6bcf0860a3841865099d0115dbcbde8b78109bd9) fix: treat non-http/https login urls as invalid
176 …3c) [#736](https://github.com/npm/cli/pull/736) add script to update dist-tags ([@mikemimik](https…
213 …fix(version): using 'allow-same-version', git commit --allow-empty and git tag -f ([@rhengles](htt…
419   add node v13 as a supported version
521   Restores ability to update packages using `--depth` as suggested by `npm audit`.
570   travis: run tests on Windows as well
620 …[npm.community#6658](https://npm.community/t/npm-ci-doesnt-fill-anymore-the-process-env-npm-config…
633   [#235](https://github.com/npm/cli/pull/235) Add spec to dist-tag remove
750 tl;dr - Fixes several issues with the cache when npm is run as `sudo` on
795     * infer uid/gid instead of accepting as options, preventing the
842       env variable for child process on Windows
870   [#212](https://github.com/npm/cli/pull/212) build: use `/usr/bin/env` to
954   [#200](https://github.com/npm/cli/pull/200) Check for `node` (as well as
1044       Ignore `.DS_Store` files as well as folders
1127   Make empty-string run-scripts run successfully as a no-op.
1164   Add `npm add` as alias to npm install in docs.
1281 `npm@6.6.0` related to the large rewrite/refactor. We're tagging it as a feature
1335 shiny, new, `window.fetch`-like
1343 * All OTP-requiring commands will now **prompt**. `--otp` is no longer required for `dist-tag`, `ac…
1395   Make `npm dist-tags` the same as `npm dist-tag ls`.
1431   Report any errors above 400 as potentially not supporting audit.
1570   maketest: Use newEnv for env production.
1636   Update OTP documentation for `dist-tag add` to clarify `--otp` is needed right
1649   Fix inline code tag issue in docs.
1721   as with third-party registries.
1749   circular dependency fix, as well as adding a proper LICENSE file.
1819   the translation layer from env variable to npm option from breaking
1897   Used `process.env` examples to make accessing certain `npm run-scripts`
1903 This is basically the same as the prerelease, but two dependencies have been
1920   prereleases. For example, `npm version premajor --preid rc` will tag a version
1983 …//arstechnica.com/gadgets/2018/07/todays-the-day-that-chrome-brands-plain-old-http-as-not-secure/)!
2007   signed, or just the tag (which is the default).
2014   Do not use `SET` to fetch the env in git-bash or Cygwin.
2145 repo as far as devDeps go.
2262 shiny new command: `npm audit`. Well, we've kept working on it since then and
2264 occasional fix, in the next few releases as more users start playing with it and
2270 -without- it! This will make a world of difference to so many people as far as
2292 want your (toplevel) dependencies to accept semver-major bumps as well, you can
2293 use `npm audit fix --force` and it'll toss those in, as well. Since it's running
2295 `--only=dev` flags, as well as things like `--dry-run`, `--json`, and
2363   Infer a version range when a `package.json` has a dist-tag instead of a
2365   dependencies to be flagged as invalid.
2381   Make sure different versions of the `Path` env var on Windows all get
2452 as `https://` URLs instead of versions.
2461   the version and use them as registry dependencies.  This lets us heal
2475   Include session and scope in requests (as we do in other requests to the registry).
2478 …Exit with non-zero status when vulnerabilities are found. So you can have `npm audit` as a test or…
2527 this might well be the last prerelease before we tag `6.0.0`! There's two major
2614   in the `package.json` as matching the entry in the `package-lock.json` and
2617   `from` field as described in [#20384](https://github.com/npm/npm/pull/20384) means
2719   Fix bug where unauthenticated errors would get reported as both 404s and
2837 By contrast, if you installed `example@~1.1.3` then you'd get `1.1.3`, as
2848 if the specifier you requested matches the `latest` tag.  If it doesn't,
2850 release candidates on tags other than `latest` and users won't see them
2851 unless they ask for them.  Promoting them is as easy as setting the `latest`
2852 tag to point at them.
2856 the `latest` tag. We're changing it to match `npm install`'s behavior.
2859   Make update and outdated respect latest interaction with semver as install does.
2874 #!/usr/bin/env node