Allow stylePreprocessorOptions - Includepaths
See original GitHub issueBeing able to specify a folder of scss files to include in components is a major asset so we don’t need to use relative paths to import a file with mixins.
{ "apps": [{ "styles": ["styles.scss"], "stylePreprocessorOptions": { "includePaths": ["styles"] } }], "defaults": { "styleExt": "scss", "component": {} } }
In the styles folder there’s a mixins file that I want to import in every component in my project, atm I need to use
@import '../../styles/mixins.scss'
instead of @import 'mixins'
Keep up the great work!
Issue Analytics
- State:
- Created 6 years ago
- Reactions:9
- Comments:6
Top Results From Across the Web
stylePreprocessorOptions includePaths do not work in 6.0.0 ...
This type of SCSS/Sass import should work out of the box. The text was updated successfully, but these errors were encountered: ...
Read more >stylePreprocessorOptions angular 8 - Stack Overflow
For existing _mixins.scss in your stylePreprocessorOptions / includePaths, use filename including first underscore @import '_mixins';.
Read more >How to simplify and clean your sass import with Angular.json
Go to angular.json file, under styles add stylePreprocessorOptions object with includePaths option and define all paths available in an ...
Read more >use "stylePreprocessorOptions.includePaths" from project.json ...
Nx Workspace: use "stylePreprocessorOptions.includePaths" from project.json to resolve include paths. 13. Relates to 2. Relates to 2 issues (2 unresolved).
Read more >Angular: You May Have Missed This - Rōnin Consulting
The stylePreprocessorOptions allows you to include additional base paths that Angular will pull in when compiling. 1. 2. 3. 4. 5. "stylePreprocessorOptions" ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you for your patience - We are launching new core technology into beta next month that should resolve this issue so this will be closed accordingly. If this issue persists, feel free to tag me or ask to reopen this issue with screenshots of the error. Thank you! 😃
Without this option it’s impossible to use scss based packages that reference other packages without prefixing the package name with ‘~’. This is quite common, for instance by the material-components-web team, see e.g. the imports in material-components/material-components-web/blob/master/packages/mdc-card/_mixins.scss.