-
Notifications
You must be signed in to change notification settings - Fork 28
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
The new update does not contains Dart Sass embedded #163
Comments
The packaging has changed in latest release, now you need to #164 will fix the confusing error message. |
My understanding (verified by some manual testing) was that npm would automatically install the correct optional dependency for the current platform. Why isn't that happening here? @alan-agius4 @ahabhgk |
@JuniorEC, can you try to remove the lock file and see if the problem persists? Which package manager and version are you using? |
I am use npm and the version is latest. i runned npm install sass-embedded-win32-x64 and this solves the problem, any dependency of my project use this lib. |
That's exactly what happened, I was investigating inside node_modules, and I didn't find it there, only after the build command, but without the module initially commented |
On my project, updating package.json with "os": [
"darwin",
"linux",
"win32"
],
"cpu": [
"x64",
"arm",
"ia32"
] and running rm -rf ./node_modules/
npm cache clear --force
npm i That updated my package-lock.json and did the trick, I can now again run It's a bit overkill, but does the job |
I'm not sure I understand—you say "that's what happened", but it sounds like you didn't get the optional dependency installed. Which is it? |
Hi everyone, I'm using sass-embedded inside a Jekyll project (Ruby) and getting a similar (?) error:
Reinstalling the gems didn't help... Any ideas? Thank you 😊❤️🙏 |
This is the repository for the Node.js embedded host, not Ruby. |
Erro occurs on build project
The folter "sass-embedded-${process.platform}-${process.arch}" is not inside on new version 1.54.8
The text was updated successfully, but these errors were encountered: