VS Code misses CSS and Sass symbols across imported files
Frontend developers using VS Code report unreliable navigation and autocomplete for CSS custom properties and Sass variables or mixins when definitions live in other files. Their projects may use these symbols across CSS, Sass, TSX, and JavaScript, but the editor and extensions they tried did not consistently resolve imports or surface suggestions. The signals are several years old, so current editor support should be checked before building.
For frontend developers using CSS and Sass in VS Code. Mentioned from Jun 2017 to Jul 2023 on GitHub.
4 different people described this problem in 3 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.5/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
We've spend two days evaluating all available extensions for simple Sass support and none of them work. I'm essentially talking about referencing variables and mixins defined in another file, imported via @import
it would be super helpful to have VSCode find all CSS files with variable definitions in and to then start prompting as soon as -- is entered in ANY file (because we not only use them in CSS, but also TSX files and even raw JavaScript via a helper)
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks