Set package.json minimum to Node 12.20#53183
Conversation
|
I think it's now or never. Let's get it in for 5.0, and if we run into issues we can consider a patch. @typescript-bot cherry-pick this to release-5.0 |
|
Heya @DanielRosenwasser, I've started to run the task to cherry-pick this into |
|
Ugh - right, forgot it doesn't say 12.20. Let's go with that. I just canceled that cherry-pick. |
|
Switched to 12.20, and I've also updated the breaking changes page to finalize this. |
|
@typescript-bot cherry-pick this to release-5.0 |
|
Heya @jakebailey, I've started to run the task to cherry-pick this into |
|
Hey @jakebailey, I've opened #53186 for you. |
Can any semi-recent version of TS actually even run on Node 4? 😆 |
|
No, absolutely not! |
…e-5.0 (#53186) Co-authored-by: Jake Bailey <[email protected]>
…to release-5.0 (microsoft#53186) Co-authored-by: Jake Bailey <[email protected]>
Previously we said 5.0 was going to be Node 10, and that's what's currently documented (though with a note that we may change it to something else https://github.com/microsoft/TypeScript/wiki/API-Breaking-Changes#typescript-50), but it seems like 12 is probably a better idea.
This might be something we want to backport so it's in 5.0 as a "breaking" change.
And maybe, it should be
12.20to give us the ability to use ESM? But, that could be on main later.