stabilize to a single minimum NodeJS LTS version for engines
#1379
Labels
breaking
CLI
enhancement
Improve something existing (e.g. no docs, new APIs, etc)
Types
Requires type definition related work / documentation
v0.33.0
Milestone
Type of Change
Enhancement
Summary
Coming out of #1202 / #1372, we opened up the range for NodeJS LTS version to try and accommodate all minimum versions with the least amount of experimental features based on the current compatibility matrix at the time
Per research into opening #1372 , here's a current breakdown of key feature we're using and where they stand in the NodeJS release / API status
import.meta.resolve
--experimental-strip-types
flag, unflagged in>=23
, Nodev22.x
unflagged backport incomingDetails
Prior to 1.0, would like to go back to a single minimum version, using
>=
so we don't have to constantly be chasing the LTS release schedule, e.g.The main items we're waiting on
import.meta.resolve
- currently RC as of20.18.x
20.18.x
I think eventually we can go to something like this for the engines field
We should also be able to clean up our test scenarios (consolidate TS tests into standard test suite) as well as swap over to using Amaro, if we can jump right to
>=22
(since for now we decided to use sucrase in #1433)The text was updated successfully, but these errors were encountered: