Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Path not resolved after adding schematics
See original GitHub issueI’m submitting a…
[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:
Current behavior
After added ng add @ngneat/tailwind no one path for scss files are resolved.
Expected behavior
I expect that the webpack it’s configured to work with all path for scss files.
Minimal reproduction of the problem with instructions
After adding the schematics if you try to create in assets folder a file that import another scss file, when run ng serve it return an error:
Error: Failed to find _scssfilename.scss_
Environment
Angular version: 11.0.0
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:5
Top Results From Across the Web
Angular Schematics relative path - Stack Overflow
I would like the newly created/updated files to be inside the /src/app/modules/foo directory instead of the root directory. Think of how ng ...
Read more >Library schematic does not support path property · Issue #16080
I tried to create a schematic that generates an application and adds a library to it. However, the library schematic does not accept...
Read more >Add schematics to Angular library | by Alain Boudard - Medium
This article is an attempt to simplify an existing documentation page from Angular, about how we can add schematics to a library.
Read more >Updating schematic component footprints from the PCB ...
Right-click on the footprint in the upper right pane and select Add to all parts. A special case is when there is no...
Read more >Schematics: Building Blocks - DEV Community
This is part 2 of Schematics: Building blocks. ... Remember, we added a required path argument in our schema when we created it....
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 Free
Top 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
I think I found another less complicated solution. As the root cause of this issue is also PostCSS 8 I used the PostCSS 7 compatible build of tailwind and replaced postcss-import with postcss-easy-import
No unfortunately I have not created a guide on this, as it is my workaround. I can create a PR to put it in the README, it’s a great idea.