-
Notifications
You must be signed in to change notification settings - Fork 13.2k
Issue35876: Give better error message when Classic Module Resolution with incorrect path #38105
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
tests/baselines/reference/errorForBareSpecifierWithImplicitModuleResolution1.errors.txt
Outdated
Show resolved
Hide resolved
|
@mshivaku99 Do you want to keep working on this? I think the next steps from @orta are pretty clear. Let us know if we can help another way. |
I can work on it this weekend! Sorry for the delay! |
|
Just as a heads up, your commits don't seem to be associated with your GitHub account. While this isn't technically a problem, you might care if you want more appropriate attribution. You can either make sure your GitHub account is associated with the email address that you're using for your commits, or rebase and amend your commits to fix the author name and email. |
… tests/cases/compiler
…incorrect path are used
|
Alright, I've addressed my feedback and given this a rebase - @DanielRosenwasser can you review? |
|
This PR has had a fresh 2nd look, just verifying that every part of the diff is needed now |
|
|
Fixes #35876