Skip to content
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

babel 7 types are incorrect #685

Closed
43081j opened this issue Sep 4, 2018 · 3 comments
Closed

babel 7 types are incorrect #685

43081j opened this issue Sep 4, 2018 · 3 comments
Labels

Comments

@43081j
Copy link
Contributor

43081j commented Sep 4, 2018

I've been doing a few small PRs in babel this week (babel/babel#8627, babel/babel#8628 and babel/babel#8629) to fix or introduce their now bundled TypeScript declarations.

I noticed a few small but breaking changes between the definitelytyped types and the official babel types for Babel 7. Figured I would raise them here for you as its possible the mismatch could mean we're missing null checks etc.

By running the analyzer build against the new types, I saw these:

I'm not sure if you guys think its important as tests pass and what not. But it means since upgrading to babel 7, we're building against incorrect types here and not handling null values in a bunch of places.

If you think its a good idea to move to babel's built in types (you cannot mix and match them with the DT types, its one or the other across all babel packages), I'm happy to have a stab at it with the analyzer at least to see how it goes at some point.

cc @rictic

@rictic
Copy link
Contributor

rictic commented Sep 12, 2018

These all look like legit bugs, we should definitely upgrade

@stale
Copy link

stale bot commented Mar 4, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Mar 4, 2020
@stale
Copy link

stale bot commented Apr 29, 2022

This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen!

@stale stale bot closed this as completed Apr 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants