作者：marco112977 | 来源：互联网 | 2023-09-09 16:36
I've done some looking around on this one, apologies if an answer is published and I missed it.
The issue: there doesn't appear to be an established best practice for working with .scss files and so on in an NX workspace.
It seems you can put them all in a directory somewhere and just do the usual long-winded imports "../../../etc/etc/variables.scss".
I'm digging into the stylePreprocessorOptions.includePaths, which as far as I know is the standard way of going about it, but I'm not having any luck, and it also seems like even if it worked, you'd have to add the frag to every project in the angular.json by hand. Not horrible but not ideal.
That's all guessing though. What's the established practice used by the NRWL team?
Thanks for any info here, I'm working with a team on adopting the extensions, want to make sure I get this one right.
该提问来源于开源项目：nrwl/nx
I would have liked this to be automated somehow, but we've been left with enough rope to hang ourselves...happy hanging
but it works now all of the above applies I noted less a few sporadic png files missed in the bundles
and the solution lies in the workspace.json where we hardwire the production app root prefix manually
1
2
3
4
5
| {
"input": "libs/shared-assets/src/assets",
"glob": "**/*",
"output": "energy/assets/"
}, |
if this is intended please validate
京公网安备 11010802041100号