You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since some package managers like pnpm do not create node_modules in the root directory of the project, simply replacing "~" in the import url with the workspace path would not work. (see
I was actually about to write a proposal to address the use of ~ - though not for this reason
From dart-sassv1.71, SASS started supporting the pkg: importer when using a specific importer[ref] (not yet implemented in Live SASS)
As long as my understanding is correct, it will allow you to use pkg: instead of ~ and it "could load packages from various different package managers"
I will write the proposal soon (maybe tonight) and reference this issue.
Also good news, I had another idea for CI builds that will be available on VS Code as a pre-release. This means when the change is ready you can start using it almost straight away
Since some package managers like pnpm do not create
node_modules
in the root directory of the project, simply replacing "~" in the import url with the workspace path would not work. (seevscode-live-sass-compiler/src/SassCompileHelper.ts
Line 21 in a44ef47
A brutal yet simple solution would be providing a means to configure the load path in.vscode/settings.json. For example
And replace "~" with the workspace root path plus all loadPaths and use the first one that exists.
The text was updated successfully, but these errors were encountered: