Skip to content
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

Cannot install due to dependency conflicts #22

Closed
TechWithTy opened this issue Mar 20, 2023 · 23 comments · May be fixed by #24 or #25
Closed

Cannot install due to dependency conflicts #22

TechWithTy opened this issue Mar 20, 2023 · 23 comments · May be fixed by #24 or #25

Comments

@TechWithTy
Copy link

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 (/workspace/CyberOniLLC-/node_modules/react-awesome-loaders/node_modules/node-gyp/lib/build.js:262:23)
npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:513:28)
npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12)
npm ERR! gyp ERR! System Linux 5.15.0-47-generic
npm ERR! gyp ERR! command "/home/gitpod/.nvm/versions/node/v16.19.0/bin/node" "/workspace/CyberOniLLC-/node_modules/react-awesome-loaders/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
npm ERR! gyp ERR! cwd /workspace/CyberOniLLC-/node_modules/react-awesome-loaders/node_modules/node-sass
npm ERR! gyp ERR! node -v v16.19.0
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! /home/gitpod/.npm/_logs/2023-03-20T16_31_49_152Z-debug-0.log

@atumas-bananamilk
Copy link

Same here.

@pbarker
Copy link

pbarker commented Jul 6, 2023

Same same

@renegadec
Copy link

anyone with a workaround the conflicts?

@Wamy-Dev
Copy link

Wamy-Dev commented Aug 8, 2023

nope, I think we just have to wait for an update

@bataevvlad
Copy link

any updates??

@krushil1
Copy link

same here. errors when installing the dependency

@Suhail-007
Copy link

facing the same issue

@ashutosh1919
Copy link
Owner

Did you try updating nodejs and npm to latest version?

@Suhail-007
Copy link

Did you try updating nodejs and npm to latest version?

Using the latest version nothing changed

@ckcherry23
Copy link

Same here

@ashutosh1919
Copy link
Owner

@Suhail-007 we use node 12. Please upgrade or downgrade your version if you have different version
Screenshot 2023-10-21 at 9 09 12 PM

@jannikstdl
Copy link

@Suhail-007 we use node 12. Please upgrade or downgrade your version if you have different version Screenshot 2023-10-21 at 9 09 12 PM

Why do you not update to the latest node version. I mean we have v18 nowerdays.

@Suhail-007
Copy link

@Suhail-007 we use node 12. Please upgrade or downgrade your version if you have different version Screenshot 2023-10-21 at 9 09 12 PM

It will break other things

@ashutosh1919
Copy link
Owner

@Suhail-007 @jnkstr Some of the packages are implemented keeping node v12 in mind. We need to have a look at it to see if we can upgrade. There may be some fixes to be done.

In the meantime, you can use nvm to use specific node version for particular project. It won't affect other projects on your computer

@Suhail-007
Copy link

@Suhail-007 @jnkstr Some of the packages are implemented keeping node v12 in mind. We need to have a look at it to see if we can upgrade. There may be some fixes to be done.

In the meantime, you can use nvm to use specific node version for particular project. It won't affect other projects on your computer

Okay, thank you very much

@RobertMurfin
Copy link

@Suhail-007 @jnkstr Some of the packages are implemented keeping node v12 in mind. We need to have a look at it to see if we can upgrade. There may be some fixes to be done.

In the meantime, you can use nvm to use specific node version for particular project. It won't affect other projects on your computer

I don't think anyone is still using v12 for new projects. Very unfortunate, your loaders are sick but 90% of the people will not be able to use this. I mean I use NextJS and it requires a minimum node version of 18.17.0, so it's impossible.

@ashutosh1919
Copy link
Owner

@RobertMurfin You are right and I am aware of it. I published this project several years ago and maintained it for 2 years. For now, I couldn't get time to fix problems and upgrade stuff. I am sorry for that. I will try in future. Meanwhile if someone is interested in fixing stuff, please feel free to raise PR.

@Suhail-007
Copy link

@RobertMurfin You are right and I am aware of it. I published this project several years ago and maintained it for 2 years. For now, I couldn't get time to fix problems and upgrade stuff. I am sorry for that. I will try in future. Meanwhile if someone is interested in fixing stuff, please feel free to raise PR.

I will try in my free time.

@CuriousCoder00
Copy link

@ashutosh1919 I'm working on updates and trying to fix the issue.

@ckcherry23
Copy link

@CuriousCoder00 You can see the discussion on PR #24 and consider continuing on the same branch if it helps.

@tahdiislam
Copy link

Same here

@Jumagova
Copy link

Jumagova commented Oct 2, 2024

I used npm i react-awesome-loaders --ignore-scripts && npm rebuild --verbose sharp and works on node v22.4.0

@divyashah0510
Copy link

Thanks @Jumagova the command really helped!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet