-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
File '@ljharb/tsconfig' not found. #363
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Why is this happening?
In the minimal reproduction provided above, it's happening because of While these errors started happening as a result of ljharb publishing these SolutionThe fix should be simple: resolve tsconfig conditionally if the real path is not in Next stepsI'm happy to accept & review a PR. It should contain a test for this case (fake dependency fixture with Locking thread to direct further conversation to PRs. |
🎉 This issue has been resolved in version 4.2.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Problem
I was using the 4.0.3 version before but since yesterday it has been reporting an error
The code and module that went wrong have been identified through both projects, but I didn't find out whose dependency this error message is from
If you use esbuild-loader with the above 2 modules in your project, you get the error
Expected behavior
Bundle Success
Minimal reproduction URL
https://stackblitz.com/edit/node-gcfggk?file=package.json
Version
v4.0.3
Node.js version
v16.0.0
Package manager
yarn
Operating system
macOS
Contributions
The text was updated successfully, but these errors were encountered: