I'm using Sage WordPress starter theme - https://github.com/roots/sage.
From today when I run yarn build (webpack --progress --config /webpack.config.js) appears this error: Module build failed: ModuleBuildError: Module build failed: Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (72) For more information on which environments are supported please see: https://github.com/sass/node-sass/releases/tag/v4.8.3
I also try to uninstall and reinstall node, npm & yarn with brew, but nothing change.
If I run npm install this is the error
../src/create_string.cpp:17:25: error: no matching constructor for initialization of 'v8::String::Utf8Value' v8::String::Utf8Value string(value); ^ ~~~~~ /Users/MYPC/.node-gyp/12.1.0/include/node/v8.h:3002:5: note: candidate constructor not viable: no known conversion from 'v8::Local<v8::Value>' to 'const v8::String::Utf8Value' for 1st argument Utf8Value(const Utf8Value&) = delete; ^ /Users/MYPC/.node-gyp/12.1.0/include/node/v8.h:2995:5: note: candidate constructor not viable: requires 2 arguments, but 1 was provided Utf8Value(Isolate* isolate, Local<v8::Value> obj); ^ 1 error generated. make: *** [Release/obj.target/binding/src/create_string.o] Error 1 gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/Users/MYPC/mysiteteam/node_modules/node-gyp/lib/build.js:262:23) gyp ERR! stack at ChildProcess.emit (events.js:196:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:256:12) gyp ERR! System Darwin 18.5.0 gyp ERR! command "/usr/local/Cellar/node/12.1.0/bin/node" "/Users/MYPC/mysiteteam/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library=" gyp ERR! cwd /Users/MYPC/mysiteteam/node_modules/node-sass gyp ERR! node -v v12.1.0 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok Build failed with error code: 1 npm WARN [email protected] requires a peer of webpack@^1.13.2 || ^2.7.0 || ^3.11.0 || ^4.4.0 but none is installed. You must install peer dependencies yourself. npm WARN [email protected] requires a peer of ajv@^5.0.0 but none is installed. You must install peer dependencies yourself. npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! **[email protected] postinstall: `node scripts/build.js`** npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] postinstall script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /Users/MYPC/.npm/_logs/2019-05-03T16_22_30_277Z-debug.log
So i'm trying to rebuild node-sass with this command line npm rebuild node-sass --force but the error it's the same!!!
More infos
2,7 GHz Intel Core i7
6.9.0
v12.1.0
1.15.2
"devDependencies": { "autoprefixer": "~8.2.0", "browser-sync": "~2.24.7", "browsersync-webpack-plugin": "^0.6.0", "bs-html-injector": "~3.0", "buble-loader": "^0.4.1", "cache-loader": "~1.2.5", "clean-webpack-plugin": "^0.1.18", "copy-globs-webpack-plugin": "^0.2.0", "css-loader": "^0.28.9", "cssnano": "~4.0.5", "eslint": "~4.19.1", "eslint-loader": "~1.9", "eslint-plugin-import": "~2.14.0", "extract-text-webpack-plugin": "~3.0.2", "file-loader": "^1.1.6", "friendly-errors-webpack-plugin": "^1.6.1", "imagemin-mozjpeg": "~7.0.0", "imagemin-webpack-plugin": "~2.2.0", "import-glob": "~1.5", "node-sass": "~4.9.4", "postcss-loader": "~2.1.0", "postcss-safe-parser": "~3.0", "resolve-url-loader": "~2.3.1", "rimraf": "~2.6", "sass-loader": "~6.0", "style-loader": "^0.22.1", "stylelint": "^8.4.0", "stylelint-config-standard": "~18.2.0", "stylelint-webpack-plugin": "^0.10.5", "uglifyjs-webpack-plugin": "^1.3.0", "url-loader": "^0.6.2", "webpack": "~3.10.0", "webpack-assets-manifest": "^1.0.0", "webpack-dev-middleware": "~2.0.4", "webpack-hot-middleware": "~2.22.3", "webpack-merge": "~4.1.4", "yargs": "~11.0.0" }, "dependencies": { "jquery": "^3.3.1", "slick-carousel": "^1.8.1", "popper.js": "^1.14.7" }
What am I doing wrong?
Another approach to fix the “Node Sass does not yet support your current environment” error would be to downgrade your Node back to the version it was when node-sass worked. You could use the nvm use [node version] command to achieve this.
Run `npm rebuild node-sass` to build the binding for your current environment. This can occur when you have compiled modules locally and checked the resulting node_modules folder into git before deploying. To fix this, we recommend removing the node_modules folder from your git repo and redeploying.
8 app running on Node 16, in which a couple of months ago we switched from node-sass to sass, as the former is deprecated. I recall at the time it took some figuring out, but in the end we just needed to install some postcss parsers to get the Nuxt app fully working with sass & sass-loader.
I'm using OSX latest version(10.14.4 (18E226)) and node 12.
While using node-sass 4.11, I had g++ error(../src/create_string.cpp:17:25: error: no matching constructor for initialization of 'v8::String::Utf8Value'
) while trying npm install
, npm rebuild
(link) which did not work.
I solved this by updating node-sass to 4.12(npm install node-sass
), as the github issue on the node-sass says that support for node 12 is implemented in 4.12 version.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With