Typescript 5.5.0 upgrade #6370
Typescript 5.5.0 upgrade #6370
Conversation
| @@ -3,7 +3,7 @@ | |||
| // we can explicitly declare `any`, but we don't want to infer `any` | |||
| "noImplicitAny": false, | |||
| // maybe bump to 'esNext'? | |||
| "target": "es6", | |||
| "target": "es2018", | |||
There was a problem hiding this comment.
how big a breaking change is this?
There was a problem hiding this comment.
And perhaps more importantly, why it's needed?
There was a problem hiding this comment.
a possible suggestion from #6366 (comment)
not sure the least breaking change way to go about this one, but also still have nice syntax
There was a problem hiding this comment.
Ah, in this case, it sounds like we were already "targetting" ES2018, only unknowingly :D Then I suppose it's not going to be a huge deal, still, worth a place in the release notes for sure.
There was a problem hiding this comment.
It's worth noting that Parcel doesn't really honour the tsconfig target anyway in its transpilation, it just aims for compatibility with the set of browsers resolved by browserslist.
Since none of the versions on that list is older than 2019, this seems like it should have zero repercussions.
|
## API Changes
unknown top level export { type: 'any' } |
Closes #6366
This just tracks a mostly working build against the next TS version.
I say mostly because node_module checks are breaking in a few libraries
benjamn/ast-types#948 - mildly concerned no activity in this repo for 8+ months, PR created benjamn/ast-types#950, because they haven't merged anything in 2+ years, I've taken the liberty of patch-packaging it, which required me to dedupe our copies of it
framer/motion#2592 - which is resolved, so updated that here
Remaining work, use stable 5.5 release when it comes out.
✅ Pull Request Checklist:
📝 Test Instructions:
🧢 Your Project: