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
Fix TypeError [ERR_INVALID_URL_SCHEME] in function-no-unknown #5918
Comments
FYI I am experiencing the same CI failure. |
Error, only on Windows (via GitHub Actions CI builds): Stylelint
Configuration:
|
The only notable change in my
|
Ah yes, I see @niksy the author of |
Just a short question: should the problem now be solved (without a new release)? In my program I removed the package-lock,json and the node_modules folder and reinstalled all packages (including stylelint-config-standard@25.0.0), but the error ("TypeError [ERR_INVALID_URL_SCHEME]: The URL must be of scheme file") is still there. In my package-lock.json I see "css-functions-list@3.0.1" (so the correct version of "css-functions-list" seems to be installed). Is there something i must do besides reinstalling my packages? |
I see it's scheduled for release 14.5.1, which isn't available on github yet. In the meantime you can set |
@BePo65 If you enable |
I have updaated all my NPM packages, unfortunately the regression bug remains. In fact, I believe the bug was introduced by ...let me try to pin |
@danielweck Have you tried |
Ah, I see it has just been published ... will try now :) |
Confirmed that this works. However, I am going to try https://www.npmjs.com/package/stylelint/v/14.5.1 now. |
Yep, all fixed now :) |
Thanks everyone for bug report, glad that we could get this resolved, and sorry for this little hiccup! |
What steps are needed to reproduce the bug?
I think there's a bug in 14.5.0. If I use
Then I get an error
What Stylelint configuration is needed to reproduce the bug?
any
How did you run Stylelint?
stylelint './src/**/*.scss' --fix
Which version of Stylelint are you using?
14.5.0
What did you expect to happen?
No script error
What actually happened?
Does the bug relate to non-standard syntax?
No response
Proposal to fix the bug
Compare with 14.4.0, it only occurs in 14.5.0
The text was updated successfully, but these errors were encountered: