You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have now updated node-sass in my project and everything started working again. Or maybe in the meantime, someone changed the version of Node on Heroku.
Note: fix has been identified and is in review. We will be verifying the fix and if it doesn't work we can revert the commit that's at fault and revisit that change. Either one should land today and an updated release will be coming out quickly.
Reacted by Artur, John-David Dalton, Al McKinlay, cybai (Haku), Jon Gjengset, Brian Cooke, Niklas Mischkulnig, Julian Simioni, Amish Shah, rehtlaw and 2 more
Our regular ci runs do not currently include adequate coverage of native modules built using the tarball. We've got an issue open to fix that and we always welcome pull requests that help.
PR for official image is still open: docker-library/official-images#4394
I noticed that even after a merge there it takes some extra time till image is really available.
Activity
mscdex commentedon May 24, 2018
My guess is that header isn't included in the headers tarball that node-gyp downloads.
jdalton commentedon May 24, 2018
More info: The Node core
core.hreference was added as part of this commit 9349e15.richardlau commentedon May 24, 2018
They (#20789 added others) aren't:
node/tools/install.py
Lines 161 to 192 in 5cbb905
I'm not sure if the correct fix is to add them to the install script, or take them out of
node.hand move them tonode_internals.h.mscdex commentedon May 24, 2018
Probably the latter.
underdarkskies commentedon May 24, 2018
pretty big bug! pls fix asap
jasnell commentedon May 24, 2018
Likely best to move the core.h reference to node_internals.h.
jasnell commentedon May 24, 2018
Actually, I take that back... fixing the install.py is likely the better choice. Investigating now.
jasnell commentedon May 24, 2018
Fix in #20925 ... once that lands a new 10.2.1 release needs to be spun up.
lokus1980 commentedon May 24, 2018
My
npm rebuild node-sassfails in production today and cannot go live with the next version promised for today :(amno1 commentedon May 24, 2018
Just updated to node 10.2 and have same issue with missing core.h header.
lokus1980 commentedon May 24, 2018
I have now updated
node-sassin my project and everything started working again. Or maybe in the meantime, someone changed the version of Node on Heroku.amno1 commentedon May 24, 2018
I just copied manually from git rep core.h into ~/node-gyp/10.2.0/include/node/, and then I also had to copy callback_scope.h and exceptions.h.
However after I did that, I got again error with include macro NODE_MODULE_X
(node::addon_register_func) (regfunc),
and my c++ module still fails to compile.
amno1 commentedon May 24, 2018
Hmm, I was able to compile with clang, but compilation with gcc fails. Everything else on my system compiles just fine with gcc :-(
jasnell commentedon May 24, 2018
Note: fix has been identified and is in review. We will be verifying the fix and if it doesn't work we can revert the commit that's at fault and revisit that change. Either one should land today and an updated release will be coming out quickly.
richardlau commentedon May 24, 2018
This was fixed by #20939 and released in 10.2.1.
3 remaining items
idibidiart commentedon May 25, 2018
hey good work guys but how could NodeJS be released without running basic tests to build popular native modules? how? explain!
jasnell commentedon May 25, 2018
Our regular ci runs do not currently include adequate coverage of native modules built using the tarball. We've got an issue open to fix that and we always welcome pull requests that help.
kigawas commentedon May 25, 2018
Our CI also got brought down by this bug....Plz fix it asap 🙏
jasnell commentedon May 25, 2018
Already fixed. Already released.
kingjerod commentedon May 25, 2018
Hmm not showing up here and my CI keeps grabbing 10.2.0
https://hub.docker.com/_/node/
jasnell commentedon May 25, 2018
Flarna commentedon May 25, 2018
PR for official image is still open: docker-library/official-images#4394
I noticed that even after a merge there it takes some extra time till image is really available.
moisadoru commentedon May 25, 2018
Here's the workaround I use until the fixed version will be available:
https://gist.github.com/moisadoru/3c894abf13474f48b5c3ce4d84a64e4e
Downgrade node until core.h issue is fixed.
Downgrade node until core.h issue is fixed.
pciavald commentedon Jun 1, 2018
I've installed node 10.2.1 to fix the core.h issue with zeromq, but i'm running into this problem :
same goes with npm
address linking problem with specific version of node
yukap6 commentedon Jan 4, 2019
in my case: node 10.2 install error, but ok with node 11.6
Replace Node 10.2.0 with 10.13.0
Actually, use 10.2.1 to workaround nodejs/node#20921