-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
node-gyp not working with node 18.12.1 #2806
Comments
Hmmmm I think this is related to isaacs/node-tar#321, but that should have been fixed in |
I have decided to workaround this issue by moving to |
I am also getting the same error... |
The workaround is to install a version of npm that has node-gyp using tar 6.1.12 or newer. I chose to use npm version 9.5.0 but there may be other versions that would work. To install a different version of npm you can simply do:
|
ok it is still not working for me..
this is the gyp file
|
Sorry, I don't have the knowledge or time to help with your specific issue. 😔 |
oh , ok Thanks :) |
Still not working here. Same issue. |
@joaocgreis Any thoughts? |
@prodkt can you be specific on in what way things aren't working for you? What do you get when you run |
I am getting this error while installing pakages. node version is 18. kindly ha
|
Please upgrade… https://github.com/nodejs/node-gyp/releases |
@cclauss thanks for your response i will try. |
@cclauss its giving node-sass error. npm ERR! code ELIFECYCLE npm ERR! A complete log of this run can be found in: |
@cclauss thanks |
OS Name: Microsoft Windows 11 Enterprise
OS Version: 10.0.22621 N/A Build 22621
System Type: ARM64-based PC
(issue seen on multiple Windows machines)
MSBuild version 17.6.0-preview-23077-01+5f95887e0 for .NET Framework
17.6.0.7701Microsoft (R) C/C++ Optimizing Compiler Version 19.36.32323 for x86
Copyright (C) Microsoft Corporation. All rights reserved.
I've been trying to rebuild native modules against Node 18.12.1, using headers for Electron 23.1.1. Things work fine on macOS and Linux. However on Windows, node-gyp frequently fails to extract headers successfully. What I have pasted below is the most common error. I have also seen node-gyp think a header did not exist after extraction, even though it does. Let me know if you'd like that error output as well.
Verbose output (from npm or node-gyp):
The text was updated successfully, but these errors were encountered: