-
Notifications
You must be signed in to change notification settings - Fork 2k
Correctly build whats-new with typescript #78762
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
Conversation
|
This PR does not affect the size of JS and CSS bundles shipped to the user's browser. Generated by performance advisor bot at iscalypsofastyet.com. |
tyxla
left a comment
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.
Looking good to me, but I agree - let's wait for #78711 to land first.
5f0eb69 to
d5ee49f
Compare
d5ee49f to
d779718
Compare
|
Turns out that we just needed to update Typescript and it works now :) I think that makes sense, as TS tweaked/updated a lot of DOM types over the several releases we just updated. |
|
I'm going to move forward with this, since CI has verified the major pieces! Happy to follow-up with feedback |
Proposed Changes
While working on #78711, I was troubleshooting a type error in this package and noticed that while it's written entirely in TS, the build system doesn't reflect that. I made various changes to the package to match other packages which are build by TS. Additionally, I removed the typings file, since none of it is needed any more.
Testing Instructions
cd packages/whats-new && yarn build-- does it work, and do files indistlook correct?To do:
HTMLElement.