-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
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
allow importing from node_modules in a mono-repo #74
Comments
The strange thing about this one, is if you remove the |
Hello
I need to import mixins to have getFont defined but don't want to have content of mixins.scss in output file.
|
same happened in one of my projects. |
@MartynasZilinskas are you looking for help on this one ? when is v4 planned for ? |
@LPCmedia, if you'd like to have a go on this, please do 👍 If you'd like us to work on this, quite a significant help would be providing a repo with a structure you're having trouble with. Or even incorporate that into tests themselves 🥇 We've also created a Gitter room for the project: |
@LPCmedia I have released a new version (canary) which includes
With that version you could try using this config:
|
Sorry a little late here but I get an error: [13:30:45] warn: [DEPRECATED]: Flag "project" usage as pointing to the config file directly is deprecated. Ignore doesnt do anything. And to be clear in our case we do want to provide the mixins from material. Let me try and get you a repro this week. |
Same problem as @LPCmedia (I want to include bootstrap mixins from the mono-repo root node_modules). Sticking to 3.0.2 for now which reoslves the imports correctly.
|
Consider a mono repo project structure like:
where the configuration:
and the index.scss contain an import:
Describe the solution you'd like
The imports are resolved to the to the top node modules.
the current result is a error:
Can't find stylesheet to import.
[12:50:54] erro: ╷
[12:50:54] erro: 363 │ @import '~@angular/material/theming';
Describe alternatives you've considered
current workaround is using a relative path on the import.
Perhaps this is documentation that is missing ?
The text was updated successfully, but these errors were encountered: