-
Notifications
You must be signed in to change notification settings - Fork 29
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
Bug: all type imports not explicitly defined. moduleResolution
setting required to import all types
#86
Comments
Hey @sambacha! Can you please provide us a reproducible example? Or this this resolve already with our latest versions? Thanks! |
Any special tsconfig/eslint config that you're using? https://stackblitz.com/edit/nextjs-nm6mbd?file=app%2Flayout.tsx Would be nice to get a reproductive example before we ship this: 9499b91 |
tscofing. |
slint config |
moduleResolution NodeNext only allows defined import paths
moduleResolution: NodeNext
only allows defined import paths
When setting
moduleResolution
intsconfig.json
to NodeNext. When this is enabled, the module resolution will only allow importing from paths that are defined within the exports config. Because only types/index.d.ts is available for import, it can cause these kinds of embedded imports to fail:VSCode
Solution
Document this tsconfig requirement. An alternative would be to ensure that all types are exported from the
types/index.d.ts
file.The text was updated successfully, but these errors were encountered: