npm cli breaking changes

[darcyclarke]

This is the issue where we file our future breaking changes for the npm cli.

Breaking Changes:

1. Remove legacy lifecycle scripts support (ie. pre/post scripts)

[wraithgar]

Copied from v10 initiative

v11 and beyond

These are still future looking breaking changes that we want to keep in consideration going forward

### Breaking Changes:
- [ ] stop reading process.env.NODE in config for nodeBin
- [ ] remove man pages
- [ ] Remove install scripts support
- [ ] Support for reading `stdin` across **all** commands (ie. https://github.com/npm/rfcs/blob/3d5b2130504139bdc8a3b599923aa07d2ff79c96/accepted/0000-dependency-selector-syntax.md#commands-could-read-from-stdin)
- [ ] Support Package Distributions by default
- [ ] Consider changing strict-ssl default based on environment variables https://github.com/npm/make-fetch-happen/pull/257
- [ ] https://github.com/npm/npm-packlist/pull/168
- [ ] Revert all of the hacks around "globstar" in packlist.  Just use node-glob's patterns.

Features (v10 or v11 or beyond):

- [ ] New `npm link` experience
- [ ] Add new "lifecycle events" API - differentiate between scripts & events - user/project & dependency defined usecases)
- [ ] First-class `import-maps` Support
- [ ] Warn/error on unecessary config items in publishConfig

[ljharb]

Let's figure out the "store the range i asked for" change for v11 too?

[wraithgar]

Repurposed this issue as the bucket for all breaking changes. Actual v11 roadmap is at #898

[ljharb]

@reggi does that last one mean that pre-existing gists might stop being npm-installable?

[wraithgar]

@ljharb it's a chesterton's fence issue. We want to explain why it's in the road and decide if we want to remove it. If you have a small gist example that could help us add an explanatory comment in our package-json parser.

ETA: it may also help us add better regression tests for this use case.

[ljharb]

Chesterton's fence says to not remove it until you can explain why it's in the road :-p

https://gist.github.com/isaacs/1837112 is the original canonical example. I'll see if I can find some modern usages.

[reggi]

🌶 take --workspace={path.basename} should work if there's only one workspace with that basename (throw if multiple)
or perhaps a different algo to do --workspace=workspace/example (tldr; I dont want to need to use the scoped package name) this already works

also --ws=xxx doesnt throw and really threw me for a loop a couple days back so either awk strings or throw if not boolean

[wraithgar]

bun.lock is now a thing npm/npm-packlist#257

[wraithgar]

#930