ui icon indicating copy to clipboard operation
ui copied to clipboard

[Bug] not working with node 16

Open ldath opened this issue 4 years ago • 1 comments

Version

master

Reproduction link

https://gitlab.com/ldath-core/examples/ex-material-dashboard/-/pipelines/430662461

Operating System

linux

Device

docker

Browser & Version

terminal

Steps to reproduce

npm install when having installed node 16

What is expected?

installing packages from package.json

What is actually happening?

npm ERR! make: *** [binding.target.mk:133: Release/obj.target/binding/src/binding.o] Error 1 npm ERR! gyp ERR! build error npm ERR! gyp ERR! stack Error: make failed with exit code: 2 npm ERR! gyp ERR! stack at ChildProcess.onExit (/builds/ldath-core/examples/ex-material-dashboard/node_modules/node-gyp/lib/build.js:262:23) npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:390:28) npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) npm ERR! gyp ERR! System Linux 5.4.109+ npm ERR! gyp ERR! command "/usr/local/bin/node" "/builds/ldath-core/examples/ex-material-dashboard/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library=" npm ERR! gyp ERR! cwd /builds/ldath-core/examples/ex-material-dashboard/node_modules/node-sass npm ERR! gyp ERR! node -v v16.13.1 npm ERR! gyp ERR! node-gyp -v v3.8.0 npm ERR! gyp ERR! not ok npm ERR! Build failed with error code: 1 npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2021-12-16T01_47_13_377Z-debug.log


Solution

looks like to old version of node-sass is used by gyp

Additional comments

ldath avatar Dec 16 '21 01:12 ldath

The error message you provided suggests that there was an issue during the build process of a package called node-sass. This error is commonly encountered when the necessary dependencies for building native modules are missing or incompatible.

npm cache clean --force

npm install

If the above steps do not resolve the issue, you can try updating the problematic package (node-sass) to the latest version. Sometimes, newer versions include bug fixes or compatibility improvements that could address the build error.

john-abdo21 avatar Aug 14 '23 03:08 john-abdo21