Materialize: Error with Meteor 1.6-rc7 and node-sass 4.5.2

Created on 12 Oct 2017  路  46Comments  路  Source: Dogfalo/materialize

Hey,

Expected Behavior

I'm updating my project for meteor 1.6 (actually rc7)

Materialize was working fine before, but now it won't install

Current Behavior

meteor install materialize:materialize
gives the following error logs :

=> Errors while adding packages:

While loading package materialize:[email protected]:
error: Command failed:
/root/.meteor/packages/meteor-tool/.1.6.0-rc.7.1w2boep++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/npm
rebuild --update-binary
Cannot download
"https://github.com/sass/node-sass/releases/download/v4.5.2/linux-x64-57_binding.node":

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.

export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

npm config set proxy http://example.com:8080
gyp info it worked if it ends with ok
gyp verb cli [
'/root/.meteor/packages/meteor-tool/.1.6.0-rc.7.1w2boep++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/node',
gyp verb cli
'/root/.meteor/packages/materialize_materialize/.0.100.2.1g1f5r6.j627++os+web.browser+web.cordova/npm/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli 'rebuild',
gyp verb cli '--verbose',
gyp verb cli '--libsass_ext=',
gyp verb cli '--libsass_cflags=',
gyp verb cli '--libsass_ldflags=',
gyp verb cli '--libsass_library=' ]
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb which succeeded python2 /usr/bin/python2
gyp verb check python version /usr/bin/python2 -c "import platform; print(platform.python_version());" returned: "2.7.3\n"
gyp verb get node dir compiling against specified --nodedir dev files:
/root/.meteor/packages/meteor-tool/.1.6.0-rc.7.1w2boep++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle
gyp verb build dir attempting to create "build" dir:
/root/.meteor/packages/materialize_materialize/.0.100.2.1g1f5r6.j627++os+web.browser+web.cordova/npm/node_modules/.temp-1nbsveb.21qf/node_modules/node-sass/build
gyp verb build dir "build" dir needed to be created?
/root/.meteor/packages/materialize_materialize/.0.100.2.1g1f5r6.j627++os+web.browser+web.cordova/npm/node_modules/.temp-1nbsveb.21qf/node_modules/node-sass/build
gyp verb build/config.gypi creating config file
gyp verb build/config.gypi writing out config file:
/root/.meteor/packages/materialize_materialize/.0.100.2.1g1f5r6.j627++os+web.browser+web.cordova/npm/node_modules/.temp-1nbsveb.21qf/node_modules/node-sass/build/config.gypi
gyp verb config.gypi checking for gypi file:
/root/.meteor/packages/materialize_materialize/.0.100.2.1g1f5r6.j627++os+web.browser+web.cordova/npm/node_modules/.temp-1nbsveb.21qf/node_modules/node-sass/config.gypi
gyp verb common.gypi checking for gypi file:
/root/.meteor/packages/materialize_materialize/.0.100.2.1g1f5r6.j627++os+web.browser+web.cordova/npm/node_modules/.temp-1nbsveb.21qf/node_modules/node-sass/common.gypi
gyp verb gyp gyp format was not specified; forcing "make"
gyp info spawn /usr/bin/python2
gyp info spawn args [
'/root/.meteor/packages/materialize_materialize/.0.100.2.1g1f5r6.j627++os+web.browser+web.cordova/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args 'binding.gyp',
gyp info spawn args '-f',
gyp info spawn args 'make',
gyp info spawn args '-I',
gyp info spawn args
'/root/.meteor/packages/materialize_materialize/.0.100.2.1g1f5r6.j627++os+web.browser+web.cordova/npm/node_modules/.temp-1nbsveb.21qf/node_modules/node-sass/build/config.gypi',
gyp info spawn args '-I',
gyp info spawn args
'/root/.meteor/packages/materialize_materialize/.0.100.2.1g1f5r6.j627++os+web.browser+web.cordova/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args '-I',
gyp info spawn args
'/root/.meteor/packages/meteor-tool/.1.6.0-rc.7.1w2boep++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/include/node/common.gypi',
gyp info spawn args '-Dlibrary=shared_library',
gyp info spawn args '-Dvisibility=default',
gyp info spawn args
'-Dnode_root_dir=/root/.meteor/packages/meteor-tool/.1.6.0-rc.7.1w2boep++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle',
gyp info spawn args
'-Dnode_gyp_dir=/root/.meteor/packages/materialize_materialize/.0.100.2.1g1f5r6.j627++os+web.browser+web.cordova/npm/node_modules/node-gyp',
gyp info spawn args '-Dnode_lib_file=node.lib',
gyp info spawn args
'-Dmodule_root_dir=/root/.meteor/packages/materialize_materialize/.0.100.2.1g1f5r6.j627++os+web.browser+web.cordova/npm/node_modules/.temp-1nbsveb.21qf/node_modules/node-sass',
gyp info spawn args '-Dnode_engine=v8',
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args 'build',
gyp info spawn args '-Goutput_dir=.' ]
gyp verb command build []
gyp verb build type Release
gyp verb architecture x64
gyp verb node dev dir
/root/.meteor/packages/meteor-tool/.1.6.0-rc.7.1w2boep++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle
gyp verb which succeeded for make /usr/bin/make
gyp info spawn make
gyp info spawn args [ 'V=1', 'BUILDTYPE=Release', '-C', 'build' ]
make: g++ : commande introuvable
make: * [Release/obj.target/libsass/src/libsass/src/ast.o] Erreur 127
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit
(/root/.meteor/packages/materialize_materialize/.0.100.2.1g1f5r6.j627++os+web.browser+web.cordova/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack at emitTwo (events.js:125:13)
gyp ERR! stack at ChildProcess.emit (events.js:213:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:200:12)
gyp ERR! System Linux 3.14.32-xxxx-grs-ipv6-64
gyp ERR! command
"/root/.meteor/packages/meteor-tool/.1.6.0-rc.7.1w2boep++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/node"
"/root/.meteor/packages/materialize_materialize/.0.100.2.1g1f5r6.j627++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
/root/.meteor/packages/materialize_materialize/.0.100.2.1g1f5r6.j627++os+web.browser+web.cordova/npm/node_modules/.temp-1nbsveb.21qf/node_modules/node-sass
gyp ERR! node -v v8.7.0
gyp ERR! node-gyp -v v3.6.1
gyp ERR! not ok
Build failed with error code: 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional
logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2017-10-12T20_13_31_117Z-debug.log

Possible Solution

As we can see in the log above, there is a 404 when trying to retrieve
https://github.com/sass/node-sass/releases/download/v4.5.2/linux-x64-57_binding.node

And that's normal, this release does not exist : https://github.com/sass/node-sass/releases/tag/v4.5.2

When I want to manually install node-sass 4.5.2, I got the same error, but it works fine with node-sass 4.5.3 which is the last release

So, a possible solution, idk if it's easy for you would be to change in package.json the node-sass version from 4.5.2 to 4.5.3

Steps to Reproduce (for bugs)

  1. Install meteor 1.6.rc7
  2. Try to install materirialize

Context

Can't install materializa with meteor

Your Environment

  • Version used: Materialize 0.100.2
  • Operating System and version (desktop or mobile): ,Debian 7.11 x86_64 GNU/Linux
    meteor 1.6 rc 7
    meteor node -v -> v8.7.0
    meteor npm -v -> 5.4.2

Thanks !

picture Zep18

Most helpful comment

Not resolved for me. I also did a fresh install of Meteor 1.6.0.1 and meteor add materialize:materialize failed as described above.

I also tried cloning the current v1-dev branch, but it failed to build with another error message (Error: ENOENT: no such file or directory, open 'E:\myproj\packages\materialize\sass\components\date_picker\_default.date.scss').

So here's my summary of workaround steps for anyone else trying to run this during their first hour with Meteor and getting frustrated with it:

  1. Create a local folder packages in your project and switch into it.
  2. Run git clone https://github.com/Dogfalo/materialize.git. You should now have a directory packages/materialize in your project.
  3. Run git checkout master.
  4. Edit the file packages/materialize/package.json and change
    "node-sass": "^4.5.2",

to

    "node-sass": "^4.5.3",
  1. Now run meteor add materialize:materialize from your project directory again. This time it should succeed!

I would really love for this to be submitted as an update to Atmosphere somehow, so the experience for newcomers like me is a bit smoother!

picture hheimbuerger on 21 Jan 2018
🎉5 👍5 ❤2 👀1

All 46 comments

Please use the summary tag of html next time ;-)

Please report this issue at https://github.com/sass/node-sass/

DanielRuf picture DanielRuf on 26 Oct 2017

Probably an error with your Meteor tools as https://github.com/sass/node-sass/releases/.../download/... is not valid anymore. It was in the past afaik.

DanielRuf picture DanielRuf on 26 Oct 2017

The same problem here with Meteor 1.6 release.

bartmichu picture bartmichu on 4 Nov 2017
👍6

Please show the error output

DanielRuf picture DanielRuf on 4 Nov 2017

Meteor 1.6 release installed with chocolatey on 64 bit Windows 10 machine. Code base from the last stable 1.5 branch. The following is the console output when I try to do meteor update.

Did you find a workaround for this problem? Right now I'm stuck with my project as I would prefer not to downgrade Meteor.

=> Errors while initializing project:

While loading package materialize:[email protected]:
error: Command failed: C:\Windows\system32\cmd.exe /c C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle\bin\npm.cmd rebuild
--update-binary
Cannot download "https://github.com/sass/node-sass/releases/download/v4.5.2/win32-ia32-57_binding.node":

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.

export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

npm config set proxy http://example.com:8080
gyp info it worked if it ends with ok
gyp verb cli [ 'C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.6.0\\mt-os.windows.x86_32\\dev_bundle\\bin\\node.exe',
gyp verb cli   'C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library=' ]
gyp info using [email protected]
gyp info using [email protected] | win32 | ia32
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle\python\python.exe" in the PATH
gyp verb `which` succeeded C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle\python\python.exe
C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle\python\python.exe
gyp verb check python version `C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle\python\python.exe -c "import platform;
print(platform.python_version());"` returned: "2.7.14\r\n"
gyp verb get node dir compiling against specified --nodedir dev files: C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle
gyp verb build dir attempting to create "build" dir:
C:\Users\michal\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1fnvasb.n4gs\node_modules\node-sass\build
gyp verb build dir "build" dir needed to be created?
C:\Users\michal\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1fnvasb.n4gs\node_modules\node-sass\build
gyp verb Not using VS2017: Could not use PowerShell to find VS2017
gyp verb build/config.gypi creating config file
gyp verb build/config.gypi writing out config file:
C:\Users\michal\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1fnvasb.n4gs\node_modules\node-sass\build\config.gypi
gyp verb config.gypi checking for gypi file:
C:\Users\michal\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1fnvasb.n4gs\node_modules\node-sass\config.gypi
gyp verb common.gypi checking for gypi file:
C:\Users\michal\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1fnvasb.n4gs\node_modules\node-sass\common.gypi
gyp verb gyp gyp format was not specified; forcing "msvs"
gyp info spawn C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle\python\python.exe
gyp info spawn args [ 'C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\node-gyp\\gyp\\gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'msvs',
gyp info spawn args   '-G',
gyp info spawn args   'msvs_version=auto',
gyp info spawn args   '-I',
gyp info spawn args
'C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\.temp-1fnvasb.n4gs\\node_modules\\node-sass\\build\\config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\node-gyp\\addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.6.0\\mt-os.windows.x86_32\\dev_bundle\\include\\node\\common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.6.0\\mt-os.windows.x86_32\\dev_bundle',
gyp info spawn args   '-Dnode_gyp_dir=C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\node-gyp',
gyp info spawn args   '-Dnode_lib_file=node.lib',
gyp info spawn args
'-Dmodule_root_dir=C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\.temp-1fnvasb.n4gs\\node_modules\\node-sass',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\.temp-1fnvasb.n4gs\\node_modules\\node-sass\\build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp verb command build []
gyp verb build type Release
gyp verb architecture ia32
gyp verb node dev dir C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle
gyp verb found first Solution file build/binding.sln
gyp verb could not find "msbuild.exe" in PATH - finding location in registry
gyp info spawn C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe
gyp info spawn args [ 'build/binding.sln',
gyp info spawn args   '/nologo',
gyp info spawn args   '/p:Configuration=Release;Platform=Win32' ]
gyp ERR! build error
gyp ERR! stack Error: `C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Users\michal\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\node-gyp\lib\build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:125:13)
gyp ERR! stack     at ChildProcess.emit (events.js:213:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Windows_NT 10.0.16299
gyp ERR! command "C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.6.0\\mt-os.windows.x86_32\\dev_bundle\\bin\\node.exe"
"C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext="
"--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\Users\michal\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1fnvasb.n4gs\node_modules\node-sass
gyp ERR! node -v v8.8.1
gyp ERR! node-gyp -v v3.6.1
gyp ERR! not ok
Build failed with error code: 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\michal\AppData\Roaming\npm-cache\_logs\2017-11-04T11_54_48_290Z-debug.log
Cannot download "https://github.com/sass/node-sass/releases/download/v4.5.2/win32-ia32-57_binding.node":

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.

export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

npm config set proxy http://example.com:8080
gyp info it worked if it ends with ok
gyp verb cli [ 'C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.6.0\\mt-os.windows.x86_32\\dev_bundle\\bin\\node.exe',
gyp verb cli   'C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library=' ]
gyp info using [email protected]
gyp info using [email protected] | win32 | ia32
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle\python\python.exe" in the PATH
gyp verb `which` succeeded C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle\python\python.exe
C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle\python\python.exe
gyp verb check python version `C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle\python\python.exe -c "import platform;
print(platform.python_version());"` returned: "2.7.14\r\n"
gyp verb get node dir compiling against specified --nodedir dev files: C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle
gyp verb build dir attempting to create "build" dir:
C:\Users\michal\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1fnvasb.n4gs\node_modules\node-sass\build
gyp verb build dir "build" dir needed to be created?
C:\Users\michal\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1fnvasb.n4gs\node_modules\node-sass\build
gyp verb Not using VS2017: Could not use PowerShell to find VS2017
gyp verb build/config.gypi creating config file
gyp verb build/config.gypi writing out config file:
C:\Users\michal\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1fnvasb.n4gs\node_modules\node-sass\build\config.gypi
gyp verb config.gypi checking for gypi file:
C:\Users\michal\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1fnvasb.n4gs\node_modules\node-sass\config.gypi
gyp verb common.gypi checking for gypi file:
C:\Users\michal\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1fnvasb.n4gs\node_modules\node-sass\common.gypi
gyp verb gyp gyp format was not specified; forcing "msvs"
gyp info spawn C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle\python\python.exe
gyp info spawn args [ 'C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\node-gyp\\gyp\\gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'msvs',
gyp info spawn args   '-G',
gyp info spawn args   'msvs_version=auto',
gyp info spawn args   '-I',
gyp info spawn args
'C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\.temp-1fnvasb.n4gs\\node_modules\\node-sass\\build\\config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\node-gyp\\addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.6.0\\mt-os.windows.x86_32\\dev_bundle\\include\\node\\common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.6.0\\mt-os.windows.x86_32\\dev_bundle',
gyp info spawn args   '-Dnode_gyp_dir=C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\node-gyp',
gyp info spawn args   '-Dnode_lib_file=node.lib',
gyp info spawn args
'-Dmodule_root_dir=C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\.temp-1fnvasb.n4gs\\node_modules\\node-sass',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\.temp-1fnvasb.n4gs\\node_modules\\node-sass\\build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp verb command build []
gyp verb build type Release
gyp verb architecture ia32
gyp verb node dev dir C:\Users\michal\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_32\dev_bundle
gyp verb found first Solution file build/binding.sln
gyp verb could not find "msbuild.exe" in PATH - finding location in registry
gyp info spawn C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe
gyp info spawn args [ 'build/binding.sln',
gyp info spawn args   '/nologo',
gyp info spawn args   '/p:Configuration=Release;Platform=Win32' ]
gyp ERR! build error
gyp ERR! stack Error: `C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Users\michal\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\node-gyp\lib\build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:125:13)
gyp ERR! stack     at ChildProcess.emit (events.js:213:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Windows_NT 10.0.16299
gyp ERR! command "C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.6.0\\mt-os.windows.x86_32\\dev_bundle\\bin\\node.exe"
"C:\\Users\\michal\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.100.2\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext="
"--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\Users\michal\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1fnvasb.n4gs\node_modules\node-sass
gyp ERR! node -v v8.8.1
gyp ERR! node-gyp -v v3.6.1
gyp ERR! not ok
Build failed with error code: 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\michal\AppData\Roaming\npm-cache\_logs\2017-11-04T11_54_48_290Z-debug.log
bartmichu picture bartmichu on 4 Nov 2017

This is a node-sass issue about a missing release/binding. Still, please contact the node-sass maintainers.

DanielRuf picture DanielRuf on 4 Nov 2017

https://github.com/sass/node-sass/

DanielRuf picture DanielRuf on 4 Nov 2017

See https://github.com/sass/node-sass/search?q=win32-ia32-57_binding.node&type=Issues&utf8=%E2%9C%93

DanielRuf picture DanielRuf on 4 Nov 2017

https://github.com/sass/node-sass/issues/2101#issuecomment-331306239

DanielRuf picture DanielRuf on 4 Nov 2017

Thanks for tracking this down. As far as I understand the problem is that Meteor 1.6 uses Node 8 which is only supported on node-sass 4.5.3 upwards. Materialize uses node-sass 4.5.2 therefore doesn't work with Meteor 1.6

If that's the case would you consider moving to a newer version of node-sass?

bartmichu picture bartmichu on 4 Nov 2017

It should be already 4.5.3 here https://github.com/Dogfalo/materialize/blob/master/package-lock.json

DanielRuf picture DanielRuf on 4 Nov 2017

But not here https://github.com/Dogfalo/materialize/blob/master/package.json

To fix the issue:

Clone materialize repo in /packages in your meteor directory, then edit package.json and edit line 51 from "node-sass": "^4.5.2", to "node-sass": "^4.5.3",

Now meteor add materialize:materialize works

Zep18 picture Zep18 on 4 Nov 2017
🎉3

The caret selector automatically updates to the latest 4.x release. See https://stackoverflow.com/questions/22343224/whats-the-difference-between-tilde-and-caret-in-package-json

Please check your lockfile if 4.5.3 is in there and which peer dependency sets this to 4.5.2

DanielRuf picture DanielRuf on 4 Nov 2017

Imo this is likely an issue with meteor which does not use the semver notation or you had an old lockfile.

DanielRuf picture DanielRuf on 4 Nov 2017

Cloning Materialize gives me package.json with 4.5.2.
Meteor works only when I manually change it to 4.5.3, as suggested.

bartmichu picture bartmichu on 5 Nov 2017

The package.json should have the caret which installs the latest 4.x release. Please also check package-lock.json. There should be still 4.5.3 like I wrote.

DanielRuf picture DanielRuf on 5 Nov 2017

@DanielRuf you are correct. There is a caret in package.json and ^4.5.3 in package-lock.json

Is there a reason not to put ^4.5.3 in package.json?

bartmichu picture bartmichu on 6 Nov 2017

The caret automatically installs the latest minor version. Without a caret it would be locked to the given version.

DanielRuf picture DanielRuf on 6 Nov 2017

Like the Ghost team does it https://github.com/TryGhost/Ghost/blob/master/package.json

DanielRuf picture DanielRuf on 6 Nov 2017

Could you specify where the packages directory is that we are supposed to clone materialize? If you are talking about the project .meteor directory there is already a packages file in there. If you are talking about the users .meteor directory: /Users/<username>/.meteoron mac, /home/<username>/.meteor on linux, andc:\Users\<username>\AppData\Local\.meteoron windows then I don't see how meteor reads the contents of the repo when downloaded to there.

Where are you cloning the repo so that when i run meteor add materialize:materialize it knows to read from the local directory where i have modified the packages.json file to force node-sass: 4.5.3 because whenever i run this command it just downloads materialize from the internet with the 4.5.2 package.json file in it.

dryhurst picture dryhurst on 14 Nov 2017

Are there any lock files?

DanielRuf picture DanielRuf on 14 Nov 2017

I will remove any pacakge-lock.json files before attempting to run meteor add materialize:materialize, but I need clarification on where to run git clone [email protected]:Dogfalo/materialize.git

dryhurst picture dryhurst on 14 Nov 2017

If you want to manually do it as I suggested, it's in "your meteor project"/packages (Create it if not exist)
I had a problem with version alpha 1, but it work when I switched to master (git checkout master)

Zep18 picture Zep18 on 14 Nov 2017
👍1

@dryhurst it works for me when I clone it into the packages folder in my project's root directory.

bartmichu picture bartmichu on 14 Nov 2017
👍1

Does it matter that node-sass in package-lock.json is under grunt-sass and not a "direct" dependency of materialize?

bartmichu picture bartmichu on 14 Nov 2017

Does it matter that node-sass in package-lock.json is under grunt-sass and not a "direct" dependency of materialize?

Probably.

DanielRuf picture DanielRuf on 14 Nov 2017

Is this something that will be fixed in the foreseeable future with a full release? This doesn't work at all as it stand with Meteor 1.6, and this include creating a brand new project. I made it work by creating a folder called "packages" under my meteor project, and cloned the master git into this new folder. After that it ran.

bprinsloo picture bprinsloo on 19 Nov 2017
👍2

Same error here on 1.6

ccornici picture ccornici on 2 Dec 2017

Updated node-sass to 4.7.2 in package.json in ecf8335.

Dogfalo picture Dogfalo on 2 Dec 2017

Is there any workaround to not being able to install this package in meteor? I tried to install the npm one but it seems to not be working as expected even tho I did:

import 'materialize-css/dist/css/materialize.min.css'
import 'hammerjs/hammer.min.js'
import 'materialize-css/dist/js/materialize.min.js'

in main.js (those are the only things I imported so far)

ccornici picture ccornici on 6 Dec 2017

@VenomCLC try npm uninstall node-sass --save-dev and then npm install node-sass --save-dev (or without -dev) or upgrade node-sass.

DanielRuf picture DanielRuf on 6 Dec 2017
👍1

Does anyone know what I need to import (from npm package since the materialize package for Meteor is still broken when trying to run "meteor add materialize:materialize") to make the Materialize Modals work? I took the first example from the Materialize website and threw it in a template and the button that should open the modal is displayed but clicking it does not open the modal, my imports are the ones that I posted 2 posts above this one, imported
BTW: the waves effect on the button works, and I have no console errors when clicking the button

ccornici picture ccornici on 12 Dec 2017

@VenomCLC did you initialize it? How is this related to node-sass?

DanielRuf picture DanielRuf on 12 Dec 2017

@DanielRuf Yes, but apparently in the wrong place (main.js, then Template.name.onCreated), I moved it now in Template.name.onRendered (hopefully this is the best practice to init js stuff) and it works.
It is related to node-sass because I'm still using the npm package instead of the atmosphere package as a workaround to the current bug that's preventing everyone from using the atmosphere package and I thought I might be missing some imports to make the npm package work and thus if anyone else would've gotten that issue they could've read this post and potentially fix it.
I also want to mention that I have low to 0 experience with npm, Meteor, atmosphere etc. and I'm trying to see how can I make all this work (npm package with meteor).
Anyway, thanks for the reply.

ccornici picture ccornici on 12 Dec 2017

While loading package materialize:[email protected]:
error: Command failed: C:\WINDOWS\system32\cmd.exe /c
C:\Users\Computer\AppData\Local.meteorpackages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\bin\npm.cmd
rebuild --update-binary
Cannot download "https://github.com/sass/node-sass/releases/download/v4.5.2/win32-x64-57_binding.node":

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.

export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

npm config set proxy http://example.com:8080
gyp info it worked if it ends with ok
gyp verb cli [
'C:\Users\Computer\AppData\Local\.meteor\packages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\bin\node.exe',
gyp verb cli
'C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\node-gyp\bin\node-gyp.js',
gyp verb cli 'rebuild',
gyp verb cli '--verbose',
gyp verb cli '--libsass_ext=',
gyp verb cli '--libsass_cflags=',
gyp verb cli '--libsass_ldflags=',
gyp verb cli '--libsass_library=' ]
gyp info using [email protected]
gyp info using [email protected] | win32 | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable
"C:\Users\Computer\AppData\Local.meteorpackages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\python\python.exe"
in the PATH
gyp verb which succeeded
C:\Users\Computer\AppData\Local.meteorpackages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\python\python.exe
C:\Users\Computer\AppData\Local.meteorpackages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\python\python.exe
gyp verb check python version
C:\Users\Computer\AppData\Local\.meteor\packages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\python\python.exe -c "import platform; print(platform.python_version());" returned: "2.7.14\r\n"
gyp verb get node dir compiling against specified --nodedir dev files:
C:\Users\Computer\AppData\Local.meteorpackages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle
gyp verb build dir attempting to create "build" dir:
C:\Users\Computer\AppData\Local.meteorpackages\materialize_materialize0.100.2\npm\node_modules.temp-1l2jdo9.jmrzj\node_modules\node-sass\build
gyp verb build dir "build" dir needed to be created?
C:\Users\Computer\AppData\Local.meteorpackages\materialize_materialize0.100.2\npm\node_modules.temp-1l2jdo9.jmrzj\node_modules\node-sass\build
gyp verb Not using VS2017: Could not use PowerShell to find VS2017
gyp verb build/config.gypi creating config file
gyp verb build/config.gypi writing out config file:
C:\Users\Computer\AppData\Local.meteorpackages\materialize_materialize0.100.2\npm\node_modules.temp-1l2jdo9.jmrzj\node_modules\node-sass\build\config.gypi
gyp verb config.gypi checking for gypi file:
C:\Users\Computer\AppData\Local.meteorpackages\materialize_materialize0.100.2\npm\node_modules.temp-1l2jdo9.jmrzj\node_modules\node-sass\config.gypi
gyp verb common.gypi checking for gypi file:
C:\Users\Computer\AppData\Local.meteorpackages\materialize_materialize0.100.2\npm\node_modules.temp-1l2jdo9.jmrzj\node_modules\node-sass\common.gypi
gyp verb gyp gyp format was not specified; forcing "msvs"
gyp info spawn
C:\Users\Computer\AppData\Local.meteorpackages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\python\python.exe
gyp info spawn args [
'C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\node-gyp\gyp\gyp_main.py',
gyp info spawn args 'binding.gyp',
gyp info spawn args '-f',
gyp info spawn args 'msvs',
gyp info spawn args '-G',
gyp info spawn args 'msvs_version=auto',
gyp info spawn args '-I',
gyp info spawn args
'C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1l2jdo9.jmrzj\node_modules\node-sass\build\config.gypi',
gyp info spawn args '-I',
gyp info spawn args
'C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\node-gyp\addon.gypi',
gyp info spawn args '-I',
gyp info spawn args
'C:\Users\Computer\AppData\Local\.meteor\packages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\include\node\common.gypi',
gyp info spawn args '-Dlibrary=shared_library',
gyp info spawn args '-Dvisibility=default',
gyp info spawn args
'-Dnode_root_dir=C:\Users\Computer\AppData\Local\.meteor\packages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle',
gyp info spawn args
'-Dnode_gyp_dir=C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\node-gyp',
gyp info spawn args '-Dnode_lib_file=node.lib',
gyp info spawn args
'-Dmodule_root_dir=C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1l2jdo9.jmrzj\node_modules\node-sass',
gyp info spawn args '-Dnode_engine=v8',
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args
'C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1l2jdo9.jmrzj\node_modules\node-sass\build',
gyp info spawn args '-Goutput_dir=.' ]
gyp verb command build []
gyp verb build type Release
gyp verb architecture x64
gyp verb node dev dir
C:\Users\Computer\AppData\Local.meteorpackages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle
gyp verb found first Solution file build/binding.sln
gyp verb could not find "msbuild.exe" in PATH - finding location in registry
gyp info spawn C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe
gyp info spawn args [ 'build/binding.sln',
gyp info spawn args '/nologo',
gyp info spawn args '/p:Configuration=Release;Platform=x64' ]
gyp ERR! build error
gyp ERR! stack Error: C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit
(C:\Users\Computer\AppData\Local.meteorpackages\materialize_materialize0.100.2\npm\node_modules\node-gyp\lib\build.js:285:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command
"C:\Users\Computer\AppData\Local\.meteor\packages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\bin\node.exe"
"C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\node-gyp\bin\node-gyp.js"
"rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd
C:\Users\Computer\AppData\Local.meteorpackages\materialize_materialize0.100.2\npm\node_modules.temp-1l2jdo9.jmrzj\node_modules\node-sass
gyp ERR! node -v v8.9.3
gyp ERR! node-gyp -v v3.6.1
gyp ERR! not ok
Build failed with error code: 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Computer\AppData\Roaming\npm-cache_logs\2017-12-13T05_47_35_946Z-debug.log
Cannot download "https://github.com/sass/node-sass/releases/download/v4.5.2/win32-x64-57_binding.node":

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.

export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

npm config set proxy http://example.com:8080
gyp info it worked if it ends with ok
gyp verb cli [
'C:\Users\Computer\AppData\Local\.meteor\packages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\bin\node.exe',
gyp verb cli
'C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\node-gyp\bin\node-gyp.js',
gyp verb cli 'rebuild',
gyp verb cli '--verbose',
gyp verb cli '--libsass_ext=',
gyp verb cli '--libsass_cflags=',
gyp verb cli '--libsass_ldflags=',
gyp verb cli '--libsass_library=' ]
gyp info using [email protected]
gyp info using [email protected] | win32 | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable
"C:\Users\Computer\AppData\Local.meteorpackages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\python\python.exe"
in the PATH
gyp verb which succeeded
C:\Users\Computer\AppData\Local.meteorpackages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\python\python.exe
C:\Users\Computer\AppData\Local.meteorpackages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\python\python.exe
gyp verb check python version
C:\Users\Computer\AppData\Local\.meteor\packages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\python\python.exe -c "import platform; print(platform.python_version());" returned: "2.7.14\r\n"
gyp verb get node dir compiling against specified --nodedir dev files:
C:\Users\Computer\AppData\Local.meteorpackages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle
gyp verb build dir attempting to create "build" dir:
C:\Users\Computer\AppData\Local.meteorpackages\materialize_materialize0.100.2\npm\node_modules.temp-1l2jdo9.jmrzj\node_modules\node-sass\build
gyp verb build dir "build" dir needed to be created?
C:\Users\Computer\AppData\Local.meteorpackages\materialize_materialize0.100.2\npm\node_modules.temp-1l2jdo9.jmrzj\node_modules\node-sass\build
gyp verb Not using VS2017: Could not use PowerShell to find VS2017
gyp verb build/config.gypi creating config file
gyp verb build/config.gypi writing out config file:
C:\Users\Computer\AppData\Local.meteorpackages\materialize_materialize0.100.2\npm\node_modules.temp-1l2jdo9.jmrzj\node_modules\node-sass\build\config.gypi
gyp verb config.gypi checking for gypi file:
C:\Users\Computer\AppData\Local.meteorpackages\materialize_materialize0.100.2\npm\node_modules.temp-1l2jdo9.jmrzj\node_modules\node-sass\config.gypi
gyp verb common.gypi checking for gypi file:
C:\Users\Computer\AppData\Local.meteorpackages\materialize_materialize0.100.2\npm\node_modules.temp-1l2jdo9.jmrzj\node_modules\node-sass\common.gypi
gyp verb gyp gyp format was not specified; forcing "msvs"
gyp info spawn
C:\Users\Computer\AppData\Local.meteorpackages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\python\python.exe
gyp info spawn args [
'C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\node-gyp\gyp\gyp_main.py',
gyp info spawn args 'binding.gyp',
gyp info spawn args '-f',
gyp info spawn args 'msvs',
gyp info spawn args '-G',
gyp info spawn args 'msvs_version=auto',
gyp info spawn args '-I',
gyp info spawn args
'C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1l2jdo9.jmrzj\node_modules\node-sass\build\config.gypi',
gyp info spawn args '-I',
gyp info spawn args
'C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\node-gyp\addon.gypi',
gyp info spawn args '-I',
gyp info spawn args
'C:\Users\Computer\AppData\Local\.meteor\packages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\include\node\common.gypi',
gyp info spawn args '-Dlibrary=shared_library',
gyp info spawn args '-Dvisibility=default',
gyp info spawn args
'-Dnode_root_dir=C:\Users\Computer\AppData\Local\.meteor\packages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle',
gyp info spawn args
'-Dnode_gyp_dir=C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\node-gyp',
gyp info spawn args '-Dnode_lib_file=node.lib',
gyp info spawn args
'-Dmodule_root_dir=C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1l2jdo9.jmrzj\node_modules\node-sass',
gyp info spawn args '-Dnode_engine=v8',
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args
'C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\.temp-1l2jdo9.jmrzj\node_modules\node-sass\build',
gyp info spawn args '-Goutput_dir=.' ]
gyp verb command build []
gyp verb build type Release
gyp verb architecture x64
gyp verb node dev dir
C:\Users\Computer\AppData\Local.meteorpackages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle
gyp verb found first Solution file build/binding.sln
gyp verb could not find "msbuild.exe" in PATH - finding location in registry
gyp info spawn C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe
gyp info spawn args [ 'build/binding.sln',
gyp info spawn args '/nologo',
gyp info spawn args '/p:Configuration=Release;Platform=x64' ]
gyp ERR! build error
gyp ERR! stack Error: C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit
(C:\Users\Computer\AppData\Local.meteorpackages\materialize_materialize0.100.2\npm\node_modules\node-gyp\lib\build.js:285:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command
"C:\Users\Computer\AppData\Local\.meteor\packages\meteor-tool\1.6.0_1\mt-os.windows.x86_64\dev_bundle\bin\node.exe"
"C:\Users\Computer\AppData\Local\.meteor\packages\materialize_materialize\0.100.2\npm\node_modules\node-gyp\bin\node-gyp.js"
"rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd
C:\Users\Computer\AppData\Local.meteorpackages\materialize_materialize0.100.2\npm\node_modules.temp-1l2jdo9.jmrzj\node_modules\node-sass
gyp ERR! node -v v8.9.3
gyp ERR! node-gyp -v v3.6.1
gyp ERR! not ok
Build failed with error code: 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Computer\AppData\Roaming\npm-cache_logs\2017-12-13T05_47_35_946Z-debug.log

Bippper picture Bippper on 13 Dec 2017
👍1

@Bipper see https://github.com/Dogfalo/materialize/issues/5275#issuecomment-348721712

DanielRuf picture DanielRuf on 13 Dec 2017

@DanielRuf do you know when a release with the fix will be available for download on Atmosphere?

ccornici picture ccornici on 13 Dec 2017

You can try git clone or dev stability.

DanielRuf picture DanielRuf on 13 Dec 2017

Or use the commit hash for the install command.

DanielRuf picture DanielRuf on 13 Dec 2017

Please close, if resolved...

tomscholz picture tomscholz on 11 Jan 2018

Not resolved for me. I also did a fresh install of Meteor 1.6.0.1 and meteor add materialize:materialize failed as described above.

I also tried cloning the current v1-dev branch, but it failed to build with another error message (Error: ENOENT: no such file or directory, open 'E:\myproj\packages\materialize\sass\components\date_picker\_default.date.scss').

So here's my summary of workaround steps for anyone else trying to run this during their first hour with Meteor and getting frustrated with it:

  1. Create a local folder packages in your project and switch into it.
  2. Run git clone https://github.com/Dogfalo/materialize.git. You should now have a directory packages/materialize in your project.
  3. Run git checkout master.
  4. Edit the file packages/materialize/package.json and change
    "node-sass": "^4.5.2",

to

    "node-sass": "^4.5.3",
  1. Now run meteor add materialize:materialize from your project directory again. This time it should succeed!

I would really love for this to be submitted as an update to Atmosphere somehow, so the experience for newcomers like me is a bit smoother!

hheimbuerger picture hheimbuerger on 21 Jan 2018
🎉5 👍5 ❤2 👀1

@Dogfalo when are you going to update the apollo's package ?

NitroBAY picture NitroBAY on 1 Apr 2018

@DanielRuf any ideas how I fix similar issue with lookback:emails please? https://github.com/lookback/meteor-emails/issues/96

From what I can see in package.json it does not use materialize just wondering if you have an recommendations please?

adamgins picture adamgins on 12 May 2018

@adamgins probably upgrade node-sass. Or what is the exact issue / error that you have got?

DanielRuf picture DanielRuf on 12 May 2018

I'm using Meteor 1.8.1 and I followed @hheimbuerger instructions except I changed the package.json to "node-sass": "^4.12.0" . Everything worked after that.

DrLonnieJonesPFMP picture DrLonnieJonesPFMP on 10 Nov 2019

So here's my summary of workaround steps for anyone else trying to run this during their first hour with Meteor and getting frustrated with it:

  1. Create a local folder packages in your project and switch into it.
  2. Run git clone https://github.com/Dogfalo/materialize.git. You should now have a directory packages/materialize in your project.
  3. Run git checkout master.
  4. Edit the file packages/materialize/package.json and change
    "node-sass": "^4.5.2",

to

    "node-sass": "^4.5.3",
  1. Now run meteor add materialize:materialize from your project directory again. This time it should succeed!

Works like a charm, but I needed to run meteor add fourseven:scss first

andrelung picture andrelung on 15 Mar 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

locomain picture locomain  路  3Comments
onigetoc picture onigetoc  路  3Comments
alexknipfer picture alexknipfer  路  3Comments
PhillippOhlandt picture PhillippOhlandt  路  3Comments
Robouste picture Robouste  路  3Comments