Upgrade to Meteor 1.10 fails #1978
Description
This is easily reproducible. However, let me start by saying that I do have a Meteor project running in 1.8. I tried upgrading to 1.10 and I get the same error when I install the angular-compiler package.
I'm running this on a Mac OS.
So to reproduce this all you have to do is as follows
meteor create --typescript
Once you've done this remove the react package and install the angular-compilers as follows:
meteor add angular-compilers
I get the following error:
16 warnings and 6 errors generated.
make: *** [Release/obj.target/binding/src/binding.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit
(/Users/andressosa/.meteor/packages/angular-compilers/.0.3.4.186be4j.x41m++os+web.browser+web.browser.legacy+web.cordova/plugin.Angular_Compilers.os/npm/node_modules/meteor/angular-scss-compiler/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack at ChildProcess.emit (events.js:311:20)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
gyp ERR! System Darwin 19.4.0
gyp ERR! command "/Users/andressosa/.meteor/packages/meteor-tool/.1.10.1.57l7nr.4f4le++os.osx.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.osx.x86_64/dev_bundle/bin/node"
"/Users/andressosa/.meteor/packages/angular-scss-compiler/.0.3.2.1s84u2i.geep++os+web.browser+web.cordova/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags="
"--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /Users/andressosa/.meteor/packages/angular-scss-compiler/.0.3.2.1s84u2i.geep++os+web.browser+web.cordova/npm/node_modules/.temp-81wa3s.a1j9a/node_modules/node-sass
gyp ERR! node -v v12.16.1
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
Build failed with error code: 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@4.7.2 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@4.7.2 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.By the looks of this it appears that the issue may be found in the node-sass postinstall script. Since meteor is using node-sass@4.7.2 and this version only supports up to version 0.10 of node. Perhaps the answer lies in moving back the version of node or somehow have meteor use the correct version.