-
Notifications
You must be signed in to change notification settings - Fork 601
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
chore: update typescript to 4.6.3 #5788
Conversation
Skip lib check issues have been resolved - updated issues noted above. |
5c3435c
to
0ee9a4d
Compare
@@ -133,7 +134,7 @@ | |||
"node-notifier": "^9.0.0", | |||
"trim-newlines": "^4.0.2", | |||
"trim": "^0.0.3", | |||
"typescript": "^3.9.0", | |||
"typescript": "^4.6.2", |
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.
This resolution forces all typescript dependencies to match. Is it still needed?
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.
I'm attempting to push forward with parity in order to keep this change as minimally disruptive as possible. My concern is that we end up with unexpected outcomes by removing this in this PR. This and it's existence as a dependency is a solid question and deserving of it's own issue IMO.
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.
I'd like to take this in a separate PR, my assumption is that it is needed due to the breaking changes within minor versions. We'll need to investigate in full though.
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.
OH api-extractor
uses its own version of Typescript without this. We don't want that.
@@ -50,6 +50,7 @@ | |||
"@types/karma": "^5.0.0", | |||
"@types/mocha": "^7.0.2", | |||
"@types/webpack-env": "^1.15.2", | |||
"@types/web-ie11": "^0.0.0", |
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.
Do we support IE11?
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.
Hard to add a reference in the package.json so I anticipated this :). The issue is specifically a break in types that creates an issue with document.createTreeWalker()
. Updating beyond 4.3.5 creates this issue so this explicitly exists to support the typing. microsoft/TypeScript#33462
This will be removed in @microsoft/fast-element
v2 as I believe the method is pulled from there.
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.
Affirmative. No more use of tree walker in 2.0.
PR is blocked by the es module update |
6d72da3
to
7aac7a3
Compare
7787eb0
to
b836568
Compare
Azure Static Web Apps: Your stage site is ready! Visit it here: https://purple-ocean-0b7ce3410-5788.centralus.azurestaticapps.net |
74102a3
to
7de16bc
Compare
@nicholasrice I'm not able to repro this build failure locally...I have no idea why - when you get a second can you pull down and see if you can repro and if so, push a fix to my branch? No idea why I can't repro this anymore locally... π€·ββοΈ |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://purple-ocean-0b7ce3410-5788.centralus.azurestaticapps.net |
Yeah I'll try to have a look today. |
@chrisdholt This also works fine on my machine. Perhaps it's some kind of dependency caching issue on the CI? |
I'm not crazy! Sounds like it could be - I'll investigate the pipelines a bit. |
9227b05
to
6417ba7
Compare
Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-coast-0df7a6610-5788.centralus.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://purple-sand-03fe10e10-5788.centralus.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-coast-0df7a6610-5788.centralus.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://purple-ocean-0b7ce3410-5788.centralus.azurestaticapps.net |
1 similar comment
Azure Static Web Apps: Your stage site is ready! Visit it here: https://purple-ocean-0b7ce3410-5788.centralus.azurestaticapps.net |
ba456ac
to
b6bcb61
Compare
Azure Static Web Apps: Your stage site is ready! Visit it here: https://purple-sand-03fe10e10-5788.centralus.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-coast-0df7a6610-5788.centralus.azurestaticapps.net |
9c57f2b
to
b6bcb61
Compare
After adding the Yarn Cache back on the build server, it seems clear that it is preventing us from passing the prepare step. I'm going to remove this and we can see about getting it back in retroactively, but currently it seems like a bug that we can't get past. |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://purple-ocean-0b7ce3410-5788.centralus.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-coast-0df7a6610-5788.centralus.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://purple-sand-03fe10e10-5788.centralus.azurestaticapps.net |
use skip lib check to avoid conflicts with fast-tooling Change files update package.json resolution for types/react because docusaurus is causing an upgrade to v18.0 update readme and yarn.lock files fix eslint errors in fast-element
# Pull Request ## π Description The Typescript version upgrade changes how it handles the @link JSDOC tag in comments causing them to be removed when the CEM Analyzer process the code. This results in the link URLs and text being rendered to markdown in such a way that they cannot be corrected into markdown links. This PR adds a CEM Analyzer plugin that checks for the existence of @link tags in the descriptions generated by "comment-parser" and retains the original text. <!--- Provide some background and a description of your work. What problem does this change solve? Is this a breaking change, chore, fix, feature, etc? --> ### π« Issues <!--- * List and link relevant issues here. --> ## π©βπ» Reviewer Notes <!--- Provide some notes for reviewers to help them provide targeted feedback and testing. Do you recommend a smoke test for this PR? What steps should be followed? Are there particular areas of the code the reviewer should focus on? --> ## π Test Plan <!--- Please provide a summary of the tests affected by this work and any unique strategies employed in testing the features/fixes. --> ## β Checklist ### General <!--- Review the list and put an x in the boxes that apply. --> - [ ] I have included a change request file using `$ yarn change` - [ ] I have added tests for my changes. - [x] I have tested my changes. - [ ] I have updated the project documentation to reflect my changes. - [ ] I have read the [CONTRIBUTING](https://github.com/Microsoft/fast/blob/master/CONTRIBUTING.md) documentation and followed the [standards](https://www.fast.design/docs/community/code-of-conduct/#our-standards) for this project. ### Component-specific <!--- Review the list and put an x in the boxes that apply. --> <!--- Remove this section if not applicable. --> - [ ] I have added a new component - [ ] I have modified an existing component - [ ] I have updated the [definition file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#definition) - [ ] I have updated the [configuration file](https://github.com/Microsoft/fast/blob/master/packages/web-components/fast-components/CONTRIBUTING.md#configuration) ## β Next Steps <!--- If there is relevant follow-up work to this PR, please list any existing issues or provide brief descriptions of what you would like to do next. -->
β¦o fix fast-animation issue
b6bcb61
to
08439bf
Compare
Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-coast-0df7a6610-5788.centralus.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://purple-sand-03fe10e10-5788.centralus.azurestaticapps.net |
1 similar comment
Azure Static Web Apps: Your stage site is ready! Visit it here: https://purple-sand-03fe10e10-5788.centralus.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-coast-0df7a6610-5788.centralus.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://purple-ocean-0b7ce3410-5788.centralus.azurestaticapps.net |
1 similar comment
Azure Static Web Apps: Your stage site is ready! Visit it here: https://purple-ocean-0b7ce3410-5788.centralus.azurestaticapps.net |
Azure Static Web Apps: Your stage site is ready! Visit it here: https://purple-ocean-0b7ce3410-5788.centralus.azurestaticapps.net |
Pull Request
π Description
closes #5198
π©βπ» Reviewer Notes
fast-components
not being a"type": "module"
.string | null
. I still like being explicit with the values when applicable for scenarios where those are the only actual valid values.Please chime in if you disagree with the approaches on the issues outlined above.
π Test Plan
β Checklist
General
$ yarn change
Component-specific
β Next Steps