| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
* fix: account for "licence" as spelling variant
|
|
|
|
Add normalize-package-data as a direct dependency to improve deduping.
|
|
First self-install!
|
|
Reinstall everything from a clean node_modules and package-lock.json
state.
Re-generate list of bundleDependencies and node_modules/.gitignore with
a script that does the right thing based on actual dependency state.
|
|
|
|
|
|
|
|
|
|
Minimum distribution size!
|
|
|
|
Correctly export bins from scoped packages using default bin naming
rules.
Credit: @iarna
PR-URL: https://github.com/npm/normalize-package-data/pull/69
|
|
Restore the ability to do one-shot upgrades from the versions of npm
bundled with Node 0.8 to npm@3, which simplifies using Travis with old
Node and new npm, for compatibility testing purposes. Older versions of
npm repack packages on install, which works poorly with the way npm@3
handles bundledDependencies with flat trees.
Fixes: #9668
PR-URL: https://github.com/npm/npm/pull/9981
|
|
|
|
Support new version of `validate-npm-package-license`.
|
|
Allow `semver@5`.
|
|
|
|
"license" now supports UNLICEN[SC]ED and "SEE LICEN[SC]E IN <filename>"
courtesy @kemitchell
PR-URL: https://github.com/npm/normalize-package-data/pull/65
|
|
Fix crasher when scripts is not an object
|
|
|
|
Incorporates validation of `package.json` license fields against the
SPDX license expression syntax, raising warnings if the license is
missing or doesn't parse as valid SPDX.
|
|
|
|
Don't prune bundledDependencies (closes #6282).
|
|
|
|
Also includes:
* normalize-package-data@1.0.1
* npm-registry-client@3.1.5
* read-package-json@~1.2.7
Treeish names containing slashes now work. Also pulled dezalgo up to a
top-level dependency, which necessitated adding it to the
bundledDependencies list.
|
|
This makes the '^' operator stricter for 0.x.y versions, even if 'x' is
not 0.
As a direct result, several *other* deps had to be updated, because they
either depended on semver 2.x, or because the new stricter rules meant
that they (or their deps) were no longer valid.
The update to 'read-installed', in particular, causes a test failure.
That update must be rolled back, or the test made to pass, prior to a
stable npm 2.0.0 release going out.
|
|
|
|
Only necessary as a dep of read-package-json
|
|
|
