Npm install keeps throwing errors when creating a new component

Developer corner
1

I tried everything to fix it, upgraded/downgraded node versions and nvm, uninstalled/re-installed etc… nothing is working and i keep getting an error relating to node-sass etc… heres a snip of the error:

npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm warn deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs
npm warn deprecated npmlog@6.0.2: This package is no longer supported.
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.1.7: Glob versions prior to v9 are no longer supported
npm warn deprecated gauge@4.0.4: This package is no longer supported.
npm warn deprecated node-sass@8.0.0: Node Sass is no longer supported. Please use sass or sass-embedded instead.
npm error code 1
npm error path /Users/mahdi/pdf-save-button/node_modules/node-sass
npm error command failed
npm error command sh -c node scripts/build.js
npm error Binary found at /Users/mahdi/pdf-save-button/node_modules/node-sass/vendor/darwin-arm64-115/binding.node

I saw online that you might need to get rid of node-sass and install sass instead, but I cant even do that because I get the same error. It looks like the @weweb/cli dependency is using node-sass and node might not support it anymore or something, I really dont know. I need to create new custom coded components and I am unable to because of that.

Is anyone else able to create a custom code component recently? Can anyone test creating a component and running npm install to check if its just me or does this need to fixed from weweb’s side??

2

what version of node are you using? try v18.

3

Thank you! That worked for my Windows computer only. I went down from v20 to v18.

I tried it on my Macbook (M2 pro chip) still throws the same error.

I mainly use my mac for developing, I hope someone can figure out why it does so on a Mac :confused:

4

not sure what are the requirements for mac.
I do custom code components since more than 2 years and everything works with both ubuntu and windows.

5

I dealt with this issue before it was a Python thing, and a Node thing, one of these. I changed version of these and it apparently worked. I don’t get the python part, but I mean, it worked.

6

python is required by node-gyp, the native addon build tool, that is required by node-sass because it requires native binaries.
you may try following the instruction of requirement installation for mac on the node-gyp docs

7

do u remember what you did with python? did u roll back the version? I tried everything with node and its not working.

So far I have been physically copying and pasting the node_modules folder from older custom components (where everything runs fine) to be able to run and develop new custom components.