Repository navigation
Preparation for v18.0.0 #42139
Description
Activity
This was discussed in the last TSC meeting, it's unlikely to happen in v18.x due to
global.cryptoalready set when using--print(e.g.node -p 'crypto.randomBytes(16).toString("hex")'). The current plan is:- Expose a new global proxy to access core modules when using
-por-eflags in v17.x (lib: expose a globalnodeproxy in eval script and REPL #42114). - Runtime deprecate global access to node core modules in v18.x
- Remove global access to core modules in v19.x – then we can enable global WebCrypto by default.
Reacted by Steven- Expose a new global proxy to access core modules when using
Should we be using project/milestones for this tracking? (I have no personal preference here.)
Should we be using project/milestones for this tracking? (I have no personal preference here.)
We can't comment/discuss in projects/milestones, though.
I have couple of PRs which would be
semver-major.
When is the deadline for this to be merged and eventually included in 18?@ShogunPanda, if they land on
masterby 2022-04-12, they should make it into the release (assuming no objections too).Refs:
Approximately two months before a major release, new vN.x and vN.x-staging branches (where N indicates the major release) should be created as forks of the master branch. Up until one week before the release date, these must be kept in sync with master.
Reacted by Paolo Insogna and lin72hI think we can close this. Thanks everyone!
Reacted by Beth Griggs and lin72hReacted by Alexei Boronine
Node.js v18.0.0 is scheduled for 2022-04-19. Let's review what needs to be done before then (semver-major changes, adapt CI, etc.)!
lib: enable global WebCrypto by default #42083child_process/promises(if possible, @aduh95 is working on it)tls: move tls.parseCertString to end-of-life #41479tls: represent registeredID numerically always #41561crypto: change default check(Host|Email) behavior #41600crypto: use RFC2253 format in PrintGeneralName #42002