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
0.9.4 breaks some Typescript configurations #1635
Comments
Thanks for the investigation! Looking into it. It could have something to do with a change to |
Let me know if I can help - I had a sniff that the helpers might be involved too but I couldn't quite see how. There are a number of typing related changes in there, so it's a bit beyond my limited current understanding of the type infra here. |
Is this theoretically fixed? I think it is but I have only seen that the playground errors now (as it should). But before I go through the variety of deps to update would love to know it was intentional :) |
Description
Something in the changes in 0.9.4 causes NodeNext module resolution to fail.
#1634
Reproduction
Node.js side, but build time so no reason browser wouldn't also be affected. I can't get the playground to fail because I don't have full control of tsconfig it seems, but here's what fails in a local build with specific tsconfig values (as described in the discussion):
Playground
Expected result
URLs should be "known" but end up just being ignored/allow any value.
Checklist
The text was updated successfully, but these errors were encountered: