-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Typescript 5.5.0 upgrade #6370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typescript 5.5.0 upgrade #6370
Changes from 1 commit
a9909c1
bce50f0
dc56e86
5e9199d
719fa8c
9ff27d5
452f18b
f0a4082
19518da
7f8312f
c7fd13a
73e0d08
88ce7f3
c22796b
d124724
1786deb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. how big a breaking change is this? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. And perhaps more importantly, why it's needed? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. a possible suggestion from #6366 (comment) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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. |
||
// allows react jsx in tsx files | ||
"jsx": "react", | ||
// Eventually turn off, one we have no more assumed default exports. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -22398,10 +22398,10 @@ typescript-strict-plugin@^2.0.0: | |
ora "^5.4.1" | ||
yargs "^16.2.0" | ||
|
||
typescript@^5.3.3: | ||
version "5.3.3" | ||
resolved "https://registry.yarnpkg.com/typescript/-/typescript-5.3.3.tgz#b3ce6ba258e72e6305ba66f5c9b452aaee3ffe37" | ||
integrity sha512-pXWcraxM0uxAS+tN0AG/BF2TyqmHO014Z070UsJ+pFvYuRSq8KH8DmWpnbXe0pEPDHXZV3FcAbJkijJ5oNEnWw== | ||
typescript@^5.5.0-dev.20240512: | ||
version "5.5.0-dev.20240512" | ||
resolved "https://registry.yarnpkg.com/typescript/-/typescript-5.5.0-dev.20240512.tgz#0125f77789f1f9cc0d1f3111523cf19ca9713e9a" | ||
integrity sha512-qaBthiey39OUkoC0p3r83WKUG4KEvgTJg968MxJ548G6lYhpsFhp1Qryxrf32BonZwzfVi46Ltb9maSHVceLMg== | ||
|
||
[email protected]: | ||
version "0.7.17" | ||
|
Uh oh!
There was an error while loading. Please reload this page.