Initiative: `v10.0.0`

[darcyclarke]

Timeline:

• Roadmap Locked-in: July 2023
• Betas/Release Candidates: July - September 2023
• Generally Available: October 2023
• End of Life: October 2024

Note: the below items are subject to change right up until July 2023

v9

Release Target: July 2023

- [ ] https://github.com/npm/statusboard/issues/672

v10

Release Target: September 2023

See #487 (comment) for breaking changes list

v11 and beyond

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

### Breaking Changes:
- [ ] 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

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

Risks

• node 16 is Eol on Sep-2023
• we should ga npm 10 atlease a month of node 20

[ljharb]

Where can we discuss using isolated mode by default? That breaks valid use cases, and I don't think it would ever be a good default behavior.