-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERR_INVALID_FILE_URL_PATH
happens when resolving alias including @
with importer
#126
Comments
I can't reproduce this: $ git clone https://github.com/sapphi-red/sass-embedded-atmark-invalid-url-reproduction
Cloning into 'sass-embedded-atmark-invalid-url-reproduction'...
remote: Enumerating objects: 12, done.
remote: Counting objects: 100% (12/12), done.
remote: Compressing objects: 100% (8/8), done.
remote: Total 12 (delta 0), reused 12 (delta 0), pack-reused 0
Receiving objects: 100% (12/12), 9.10 KiB | 4.55 MiB/s, done.
$ cd sass-embedded-atmark-invalid-url-reproduction/
$ npm i
added 69 packages, and audited 70 packages in 2s
8 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
$ node sass.js
[dart-sass]
.bar {
color: blue;
}
.foo {
color: red;
}
-----------
[sass-embedded]
.bar {
color: blue;
}
.foo {
color: red;
}
|
Thanks for taking a look. Look like this only happens on windows. |
Okay, I can reproduce this now. Here's what's going on under the covers:
Note that the |
Thank you for the fix! |
When resolving alias including
@
with importer,ERR_INVALID_FILE_URL_PATH
happens.The implementation of importer is below.
Also I am using legacy
render
function.This works well with dart-sass.
Error message
Step to reproduce
npm i
.node sass.js
dart-sass
runs with no error.sass-embedded
fails with error.Additional context
I was trying to use
sass-embedded
with vite (vitejs/vite#6734).I used
npm i -D sass@npm:sass-embedded@latest
to install/replace it.Then I tried but this error occured. So I created a minimal reproduction without vite.
The text was updated successfully, but these errors were encountered: