-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initiative: v11.0
#488
Comments
Copied from v10 initiative v11 and beyondThese are still future looking breaking changes that we want to keep in consideration going forward
Features (v10 or v11 or beyond):
|
Let's figure out the "store the range i asked for" change for v11 too? |
I just lost an hour of my day to this "clever" helpful line. We should drop support for this. https://github.com/npm/cli/blob/1114a12f2b4691d403d0863d4dca44f25580f57d/lib/cli-entry.js#L9-L12 // if npm is called as "npmg" or "npm_g", then run in global mode.
if (process.argv[1][process.argv[1].length - 1] === 'g') {
process.argv.splice(1, 1, 'npm', '-g')
} $ node /Users/wraithgar/Development/npm/cli/branches/gar_semver-debug pkg set description='test'
npm ERR! code EPKGGLOBAL
npm ERR! There's no package.json file to manage on global mode |
A few things I've found in the issue tracker lately that can't be fixed due to how they would likely break things:
|
We should remove the npm audit fallback to the old endpoint. I don't think it works with lockfile v3 anyways. |
Now that hooks is deprecated, and I don't think any other registries support it, it should be removed in npm 11 |
We will also need to update documentation regarding hooks |
Timeline:
Breaking Changes:
pre
/post
scripts)The text was updated successfully, but these errors were encountered: