Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
fix(typescript-eslint): handlefile://
urls in stack trace when inferringtsconfigRootDir
#11464
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
fix(typescript-eslint): handlefile://
urls in stack trace when inferringtsconfigRootDir
#11464
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Thanks for the PR,@kirkwaiblinger! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently onhttps://opencollective.com/typescript-eslint. |
netlifybot commentedAug 6, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
✅ Deploy Preview fortypescript-eslint ready!
To edit notification comments on pull requests, go to yourNetlify project configuration. |
file://
urls in stack trace APIfile://
urls in stack trace when inferringtsconfigRootDir
nx-cloudbot commentedAug 6, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
View yourCI Pipeline Execution ↗ for commit740b45d
☁️Nx Cloud last updated this comment at |
codecovbot commentedAug 6, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@## main #11464 +/- ##======================================= Coverage 90.88% 90.88% ======================================= Files 505 505 Lines 51121 51125 +4 Branches 8413 8415 +2 =======================================+ Hits 46459 46463 +4 Misses 4648 4648 Partials 14 14
Flags with carried forward coverage won't be shown.Click here to find out more.
🚀 New features to boost your workflow:
|
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.
pls add a test
"\\(#.+?\\)" | ||
], | ||
"words": [ | ||
"AFAICT", |
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 feels like it should be in the cspell dictionary 😂
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.
👌
7319bad
intotypescript-eslint:mainUh oh!
There was an error while loading.Please reload this page.
PR Checklist
project: true
and imported config #11429Overview
I haven't written an automated test for this, since... it's not super clear how without mocking the v8 stack trace API (which seems really yucky) or writing a full integration test (tedious).
But it's very easy to clone down the repo in#11429,
yarn link
, and observe the bug being fixed.Maybe more comprehensive automated testing of the
tsconfigRootDir
can be a follow-on if we want to invest in that effort?