You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After reading Typescript Types in beta 6 and Declaring typings for modules in subfolders I still can't figure out how to add material-ui@next types to my project.
Adding "material-ui" to "types' in my tsconfig doesn't work and the only workable solution I've found is adding node_modules/**/*.d.ts to my "include" but when I do that I can't anymore import files using an absolute path.
Basically I can't do
import Component from "lib/Component";
but I have to use a relative path "./src/lib/Component"
Cheers
Tech
Version
"material-ui": "^1.0.0-beta.43",
TypeScript 2.8
The text was updated successfully, but these errors were encountered:
We use the issue tracker exclusively for bug reports and feature requests, however,
this issue appears to be a support request or question. Please ask on StackOverflow where the
community will do their best to help. There is a "material-ui" tag that you can use to tag your
question.
If you would like to link from here to your question on SO, it will help others find it.
If your issues is confirmed as a bug, you are welcome to reopen the issue using the issue template.
Thank you very much.
I've compared the tsconfig from the example and the one in my project.
No need for types or includes the fix is "moduleResolution": "node".
For reference my tsconfig:
After reading Typescript Types in beta 6 and Declaring typings for modules in subfolders I still can't figure out how to add material-ui@next types to my project.
Adding "material-ui" to "types' in my tsconfig doesn't work and the only workable solution I've found is adding node_modules/**/*.d.ts to my "include" but when I do that I can't anymore import files using an absolute path.
Basically I can't do
import Component from "lib/Component";
but I have to use a relative path "./src/lib/Component"
Cheers
The text was updated successfully, but these errors were encountered: