[css] Custom aliases in CSS file resolution
See original GitHub issuePlease read from tsconfig
/jsconfig
to resolve SCSS modules. My suggestion to make this reliable is to simply only allow the import aliases to work inside of an aliased directory, and in every subfolder starting from the tsconfig
/jsconfig
as the root, so that we can theoretically open huge projects with weird build settings and have a sane default for it. The tsconfig
/jsconfig
essentially define majority of these weird quirks such as these path aliases for the entire IDE, and we should just stick to allowing this to continue even if it “makes no sense” to read from these files for what is “just SCSS”.
If this won’t be supported, we could at least make it possible to define these aliases in the .vscode settings.json and then use those paths across the IDE as the standard. No matter what though, we need these path aliases as for large projects not being able to jump to the definition of an imported module is very annoying.
Issue Analytics
- State:
- Created a year ago
- Reactions:30
- Comments:8 (2 by maintainers)
Top GitHub Comments
The description says:
to resolve SCSS modules
Why the name change? Imports being resolved in this way should be supported for all CSS formats, not just SCSS.