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.

Please provide a more detailed Information Sheet/Readme about styleIncludePaths.

See original GitHub issue

Type of Issue

[ ] Bug Report
[ X ] Feature Request

Description

I have opened a Thread on Stackoverflow regarding this Issue.

Thank you

Issue Analytics

State:
Created 3 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

alan-agius4commented, Aug 22, 2020

The includes paths are used by CSS processors during the build of a library to resolve imports when processing scss/less/stylus files.

In your ship unprocessed scss files, these paths will need to be included at application level instead of the library level, because such files will not be handled by the library build pipeline, but the application’s. They are just copied as static files.

In case you don’t want to include such paths at application level, you can leverage webpack’s tilde import syntax ex: @import "~/my-lib/scss/mixins”.

Note: webpack specific features are not official supported by the Angular tooling team and might break without warning.

0reactions

github-actions[bot]commented, Sep 24, 2020

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

_{This action has been performed automatically by a bot.}