-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Unify default import resolution across specifier target codepaths #49814
Unify default import resolution across specifier target codepaths #49814
Conversation
@weswigham Is there any chance to move this PR forward? The behavior confused a lot of people who are trying to use TS with ESM. Love to see if there are any updates 😁 |
How about cherry-picking this fix into the 4.8 branch? I found it still a problem in new released 4.8.2. |
@typescript-bot cherry-pick this to release-4.8 |
Heya @RyanCavanaugh, I've started to run the task to cherry-pick this into |
Hey @RyanCavanaugh, I couldn't open a PR with the cherry-pick. (You can check the log here). You may need to squash and pick this PR into release-4.8 manually. |
@typescript-bot cherry-pick this to release-4.8 |
Heya @weswigham, I've started to run the task to cherry-pick this into |
Hey @weswigham, I've opened #50578 for you. |
Component commits: e2d22fa Unify default import resolution across specifier target codepaths b341699 Merge main into branch cf010b5 Use differing type aliases, per request Co-authored-by: Wesley Wigham <[email protected]>
Fixes #49567