-
-
Notifications
You must be signed in to change notification settings - Fork 431
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
v9.4.0 cannot resolve .d.ts files #1504
Comments
Ran into exactly the same issue today. ts-loader@9.4.0 was resolving a local file instead of a |
This was likely caused by #1503 @manuth would you be able to take a look please? If we can resolve this quickly that'd be great - if we can't then we'll likely have to revert 9.4.0 for now. For others bumping on this, please pin to 9.3.1 for now. We'll look to either revert or fix in the near future. @falsandtru thanks for the repro. |
We could go forward and disable I will try to work it out using your repository, @falsandtru. |
@falsandtru Sadly I could not find myself able to reproduce the issue. For me, the command Could you please tell me how to reproduce the issue? Is there any other repository or code example causing this error? |
@xemlock could you please tell me on which repository and what branch you're facing this issue? |
@manuth I already fixed the issue on master branch. Please use the commit written in #1504 (comment). Or revert the change falsandtru/pjax-api@23f3db5 |
@falsandtru Thank you so much for providing your example workspace! I could pinpoint the issue and will fix it asap. |
ts-loader was able to resolve
index.d.ts
fromindex.ts
until v9.3.1, but cannot do it since v9.4.0. The errors occurs on Ubuntu 20.04 but doesn't on Windows 10.Expected Behaviour
no error
Actual Behaviour
https://github.com/falsandtru/pjax-api/actions/runs/3081442336/jobs/4980275627
Steps to Reproduce the Problem
Check out falsandtru/pjax-api@76ad376 on Ubuntu.
Run
npm i && npm run dist
.Location of a Minimal Repository that Demonstrates the Issue.
falsandtru/pjax-api@76ad376
The text was updated successfully, but these errors were encountered: