Open pcj opened 7 years ago
Figured it out: need to prefix with external/
, such as:
@import "external/com_github_milligram_milligram/milligram";
Will leave this open and close it with a PR to the README.
@pcj this worked for us too, but it also broke build sandboxing for us.
Just adding that you can see the contents of the external/
dir using bazel info execution_root
. I didn't know the exact path to import until I looked there:
cd `bazel info execution_root`
ls external
Thanks for the pointers. This works for the resulting files, but the map file displays a directory that the clients don't like as much:
"sources":["../../../../../../../external/pure.css/file/pure.css","../../../../../../../external/grids-responsive.css/file/grids-responsive.css","../../../../../../../src/hthing/web/static/styles.scss"]
In my case, ideally this should only be
"sources":["pure.css","grids-responsive.css","styles.scss"]
Any pointers how to generate a "resolved" source map?
Given an external repository definition like so, I'm struggling to figure out what the correct
@import
path would be for the external sass_library. For example: