Age | Commit message (Collapse) | Author |
|
This includes the npa git-parsing patch to make it so
non-hosted SCP-style identifiers are correctly handled.
Previously, npa would mangle them (even though hosted-git-info
is doing the right thing for them).
Fixes: https://github.com/npm/npm/issues/16726
|
|
|
|
|
|
|
|
Add `escapedName` to the result. It is suitable for passing through to a
registry without further processing.
Credit: @nexdrew
|
|
Fixes some Windows-related stuff
Credit: @zkat
PR-URL: https://github.com/npm/npm/pull/11444
Reviewed-By: @zkat
Reviewed-By: @iarna
Reviewed-By: @othiym23
|
|
Fix some file:// urls on windows
Stop resolving local paths in npa (this is now done in
realze-package-specifier)
Credit: @zkat
|
|
PR-URL: https://github.com/npm/npm-package-arg/pull/15
Credit: @zkat
Fixes: #10189
|
|
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
|
|
Allow `semver@5`.
|
|
Remove browser artifacts from distribution.
|
|
|
|
|
|
|
|
|
|
Use `hosted-git-info` directly to ensure that all GitHub URLs are being
run through the same cloning strategy for caching. Fixes #7630.
|
|
Do the minimal upgrade necessary to get tests passing with new hosted
repo metadata. I anticipate the realize-package-specifier update will be
a little more invasive.
|
|
Bring in the latest version with fixed tests
|
|
support git+file:// URLs for local bare repos
|
|
|
|
support file URIs as local specs
|
|
Work better with git treeishes with slashes in them.
|
|
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.
|
|
|
|
|
|
|