-
Notifications
You must be signed in to change notification settings - Fork 789
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
feat(typescript): upgrade to TypeScript 5 #4315
Changes from all commits
9b07a37
08a3902
40f90e3
e341142
58b0a00
98c4f7e
2be474e
6670a68
75f77a1
15620fc
61e42e4
bbc8aa7
0385538
7842fdd
29b03f1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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. As far as dependency updates go that modify the AST, the normal suspects all look up to date (Prettier, ESLint, typescript-eslint). I think in order to support this internally, we may need to bump |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this a legit solution to the
Object.defineProperty
thing? Basically what I've done is add a bit to the typescript source plugin which writes a file toscripts/build/typescript-modified-for-jest.js
with a subset of the changes we do for building stencil itself. Then we use the module name mapping thingy to re-point imports oftypescript
in either spec files or files which are imported by specfiles (and not already mapped to built output) to that built file. This lets us keep using things likepatchTypescript
in tests.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The way the control flow goes in that plugin this file will be regenerated on disk any time that the other typescript file (which is bundled into the
compiler
bundle) will be regenerated, so I believe that if we upgrade to a point release or something it should work without trouble. Of course, annpm run clean
will also just get rid of it too.