Permalink
Switch branches/tags
{{ refName }}
default
latest
Could not load branches
Nothing to show
Could not load tags
Nothing to show
{{ refName }}
default
Commits on Oct 5, 2022
-
-
-
-
-
chore: use packlist to write node_module ignores (#5363)
The gitignore file inside `node_modules/` is now an allow list built from the output of `npm-packlist`. This means that the only dependencies that get checked in to source control are those that will end up in the packed tarball, with the exception of some files that we always ignore. This also moves the dependencies required to build the docs workspace from devDependencies to dependencies so they are available for making the docs after pruning. Ignoring these from source control was the reason that the change to how we build the gitignore file was necessary.
-
chore: @npmcli/template-oss@4.5.0 (#5646)
This also removes the release-manager script in favor of the one provided by template oss.
-
-
-
Commits on Oct 4, 2022
-
-
-
docs: remove link to cache command (#5637)
The cache command itself contains this config making it a circular reference
-
-
-
-
-
Commits on Oct 3, 2022
Commits on Sep 30, 2022
-
-
-
feat: implement new
npm-packlistbehaviorThis also lands the latest `pacote` which now requires passing in an `Arborist` constructor for use in loading the package tree that gets passed to `npm-packlist`. BREAKING CHANGE: `npm pack` now follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.
Commits on Sep 29, 2022
-
-
feat: default access to
publicBREAKING CHANGE: The default value of `access` is now `public`
Commits on Sep 27, 2022
-
chore(make): docs should come before test during publish
docs needs to rebuild cmark-gfm which needs to be present in order to run tests
-
feat: write eresolve error files to the logs directory
Also refactor all files written to the logs directory to use the same code path for file name creation.
-
feat: timings are now written alongside debug log files
BREAKING CHANGE: `--timing` file changes: - When run with the `--timing` flag, `npm` now writes timing data to a file alongside the debug log data, respecting the `logs-dir` option and falling back to `<CACHE>/_logs/` dir, instead of directly inside the cache directory. - The timing file data is no longer newline delimited JSON, and instead each run will create a uniquely named `<ID>-timing.json` file, with the `<ID>` portion being the same as the debug log. - Finally, the data inside the file now has three top level keys, `metadata`, `timers, and `unfinishedTimers` instead of everything being a top level key. Closes npm/statusboard#456