We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Importing scss modules using module path aliases does not give typesafety if type declarations are put in a seperate output folder.
// Works import styles from "../styles/Home.module.scss"; // Does not work import styles from "@/styles/Home.module.scss";
Type safety should be present when using module path aliases and type definitions are put in a seprate output folder.
No typesafety when using module path aliases and type definitions are put in a seprate output folder.
Maybe there is some tsconfig setting that I am missing.
Codesandbox link
Using Typescript Workspace version 5.4.5
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Importing scss modules using module path aliases does not give typesafety if type declarations are put in a seperate output folder.
Expected Behavior
Type safety should be present when using module path aliases and type definitions are put in a seprate output folder.
Current Behavior
No typesafety when using module path aliases and type definitions are put in a seprate output folder.
Possible Solution
Maybe there is some tsconfig setting that I am missing.
Steps to Reproduce (for bugs)
Codesandbox link
Your Environment
Using Typescript Workspace version 5.4.5
The text was updated successfully, but these errors were encountered: