Materialize: Cannot install Materialize meteor package
Description
Installing the meteor package materialize:materialize even on an empty repo fails. I reinstalled Meteor, it didn't solve my issue.
Repro Steps
meteor create test
To create a basic empty meteor app.
meteor add materialize:materialize
Very long error message :
=> Errors while adding packages:
While loading package materialize:[email protected]:
error: Command failed:
C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\bi
n\npm.cmd
rebuild --update-binary
node-pre-gyp ERR! Tried to download:
https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.15/fse-v1.0.15-node-v46-win32-ia32.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and [email protected] (node-v46
ABI) (falling back to source compile with node-gyp)
Traceback (most recent call last):
File
"C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\gyp\gyp_main.py",
line 16, in <module>
sys.exit(gyp.script_main())
File
"C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\gyp\pylib\gyp\__init__.py",
line 545, in script_main
return main(sys.argv[1:])
File
"C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\gyp\pylib\gyp\__init__.py",
line 538, in main
return gyp_main(args)
File
"C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\gyp\pylib\gyp\__init__.py",
line 523, in gyp_main
generator.GenerateOutput(flat_list, targets, data, params)
File
"C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py",
line 2003, in GenerateOutput
sln_projects, project_objects, flat=msvs_version.FlatSolution())
File
"C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py",
line 1762, in _GatherSolutionFolders
return _DictsToFolders('', root, flat)
File
"C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py",
line 1715, in _DictsToFolders
for folder, contents in bucket.iteritems():
AttributeError: 'MSVSProject' object has no attribute 'iteritems'
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit
(C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\lib\configure.js:305:16)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:12)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command
"C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.4.2_3\\mt-os.windows.x86_32\\de
v_bundle\\bin\\node.exe"
"C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.4.2_3\\mt-os.windows.x86_32\\de
v_bundle\\lib\\node_modules\\node-gyp\\bin\\node-gyp.js"
"configure" "--fallback-to-build"
"--module=C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.98.0\\npm\
\node_modules\\.temp-1jdosff\\node_modules\\fsevents\\lib\\binding\\Release\\node-v46-win32-ia32\\f
se.node"
"--module_name=fse"
"--module_path=C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.98.0\
\npm\\node_modules\\.temp-1jdosff\\node_modules\\fsevents\\lib\\binding\\Release\\node-v46-win32-ia
32"
gyp ERR! cwd
C:\Users\Ilan\AppData\Local\.meteor\packages\materialize_materialize\0.98.0\npm\node_modules\.temp-
1jdosff\node_modules\fsevents
gyp ERR! node -v v4.6.2
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute
'C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\b
in\node.exe
C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\li
b\node_modules\node-gyp\bin\node-gyp.js
configure --fallback-to-build
--module=C:\Users\Ilan\AppData\Local\.meteor\packages\materialize_materialize\0.98.0\npm\node_modul
es\.temp-1jdosff\node_modules\fsevents\lib\binding\Release\node-v46-win32-ia32\fse.node
--module_name=fse
--module_path=C:\Users\Ilan\AppData\Local\.meteor\packages\materialize_materialize\0.98.0\npm\node_
modules\.temp-1jdosff\node_modules\fsevents\lib\binding\Release\node-v46-win32-ia32'
(1)
node-pre-gyp ERR! stack at ChildProcess.<anonymous>
(C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
node-pre-gyp ERR! stack at emitTwo (events.js:87:13)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:172:7)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:854:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:222:5)
node-pre-gyp ERR! System Windows_NT 10.0.14393
node-pre-gyp ERR! command
"C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.4.2_3\\mt-os.windows.x86_32\\de
v_bundle\\bin\\node.exe"
"C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.4.2_3\\mt-os.windows.x86_32\\de
v_bundle\\lib\\node_modules\\node-pre-gyp\\bin\\node-pre-gyp"
"install" "--fallback-to-build"
node-pre-gyp ERR! cwd
C:\Users\Ilan\AppData\Local\.meteor\packages\materialize_materialize\0.98.0\npm\node_modules\.temp-
1jdosff\node_modules\fsevents
node-pre-gyp ERR! node -v v4.6.2
node-pre-gyp ERR! node-pre-gyp -v v0.6.30
node-pre-gyp ERR! not ok
npm ERR! Windows_NT 10.0.14393
npm ERR! argv
"C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.4.2_3\\mt-os.windows.x86_32\\de
v_bundle\\bin\\node.exe"
"C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.4.2_3\\mt-os.windows.x86_32\\de
v_bundle\\lib\\node_modules\\npm\\bin\\npm-cli.js"
"rebuild" "--update-binary"
npm ERR! node v4.6.2
npm ERR! npm v3.10.9
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-pre-gyp install
--fallback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the fsevents package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs fsevents
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls fsevents
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!
C:\Users\Ilan\AppData\Local\.meteor\packages\materialize_materialize\0.98.0\npm\node_modules\.temp-
1jdosff\npm-debug.log
node-pre-gyp ERR! Tried to download:
https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.15/fse-v1.0.15-node-v46-win32-ia32.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and [email protected] (node-v46
ABI) (falling back to source compile with node-gyp)
Traceback (most recent call last):
File
"C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\gyp\gyp_main.py",
line 16, in <module>
sys.exit(gyp.script_main())
File
"C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\gyp\pylib\gyp\__init__.py",
line 545, in script_main
return main(sys.argv[1:])
File
"C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\gyp\pylib\gyp\__init__.py",
line 538, in main
return gyp_main(args)
File
"C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\gyp\pylib\gyp\__init__.py",
line 523, in gyp_main
generator.GenerateOutput(flat_list, targets, data, params)
File
"C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py",
line 2003, in GenerateOutput
sln_projects, project_objects, flat=msvs_version.FlatSolution())
File
"C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py",
line 1762, in _GatherSolutionFolders
return _DictsToFolders('', root, flat)
File
"C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py",
line 1715, in _DictsToFolders
for folder, contents in bucket.iteritems():
AttributeError: 'MSVSProject' object has no attribute 'iteritems'
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit
(C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-gyp\lib\configure.js:305:16)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:12)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command
"C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.4.2_3\\mt-os.windows.x86_32\\de
v_bundle\\bin\\node.exe"
"C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.4.2_3\\mt-os.windows.x86_32\\de
v_bundle\\lib\\node_modules\\node-gyp\\bin\\node-gyp.js"
"configure" "--fallback-to-build"
"--module=C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.98.0\\npm\
\node_modules\\.temp-1jdosff\\node_modules\\fsevents\\lib\\binding\\Release\\node-v46-win32-ia32\\f
se.node"
"--module_name=fse"
"--module_path=C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\materialize_materialize\\0.98.0\
\npm\\node_modules\\.temp-1jdosff\\node_modules\\fsevents\\lib\\binding\\Release\\node-v46-win32-ia
32"
gyp ERR! cwd
C:\Users\Ilan\AppData\Local\.meteor\packages\materialize_materialize\0.98.0\npm\node_modules\.temp-
1jdosff\node_modules\fsevents
gyp ERR! node -v v4.6.2
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute
'C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\b
in\node.exe
C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\li
b\node_modules\node-gyp\bin\node-gyp.js
configure --fallback-to-build
--module=C:\Users\Ilan\AppData\Local\.meteor\packages\materialize_materialize\0.98.0\npm\node_modul
es\.temp-1jdosff\node_modules\fsevents\lib\binding\Release\node-v46-win32-ia32\fse.node
--module_name=fse
--module_path=C:\Users\Ilan\AppData\Local\.meteor\packages\materialize_materialize\0.98.0\npm\node_
modules\.temp-1jdosff\node_modules\fsevents\lib\binding\Release\node-v46-win32-ia32'
(1)
node-pre-gyp ERR! stack at ChildProcess.<anonymous>
(C:\Users\Ilan\AppData\Local\.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\l
ib\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
node-pre-gyp ERR! stack at emitTwo (events.js:87:13)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:172:7)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:854:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:222:5)
node-pre-gyp ERR! System Windows_NT 10.0.14393
node-pre-gyp ERR! command
"C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.4.2_3\\mt-os.windows.x86_32\\de
v_bundle\\bin\\node.exe"
"C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.4.2_3\\mt-os.windows.x86_32\\de
v_bundle\\lib\\node_modules\\node-pre-gyp\\bin\\node-pre-gyp"
"install" "--fallback-to-build"
node-pre-gyp ERR! cwd
C:\Users\Ilan\AppData\Local\.meteor\packages\materialize_materialize\0.98.0\npm\node_modules\.temp-
1jdosff\node_modules\fsevents
node-pre-gyp ERR! node -v v4.6.2
node-pre-gyp ERR! node-pre-gyp -v v0.6.30
node-pre-gyp ERR! not ok
npm ERR! Windows_NT 10.0.14393
npm ERR! argv
"C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.4.2_3\\mt-os.windows.x86_32\\de
v_bundle\\bin\\node.exe"
"C:\\Users\\Ilan\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.4.2_3\\mt-os.windows.x86_32\\de
v_bundle\\lib\\node_modules\\npm\\bin\\npm-cli.js"
"rebuild" "--update-binary"
npm ERR! node v4.6.2
npm ERR! npm v3.10.9
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-pre-gyp install
--fallback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the fsevents package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs fsevents
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls fsevents
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!
C:\Users\Ilan\AppData\Local\.meteor\packages\materialize_materialize\0.98.0\npm\node_modules\.temp-
1jdosff\npm-debug.log
NitroBAY
All 49 comments
The problem is that Materialize tries to install fsevents but I use Windows not mac.
NitroBAY
on 6 Feb 2017
Possible workaround : downloading the repo, putting it in the /packages folder so meteor add materialize:materialize install a local version, what is actually working.
NitroBAY
on 6 Feb 2017
Is their a meteor command to install without installing fsevents?
I'm having same issue as above on windows 10 64.
muffinrecon
on 7 Feb 2017
Did you try installing fourseven:scss first?
meteor add fourseven:scss
Dogfalo
on 7 Feb 2017
@Dogfalo , Yes, I'm having the same issue after installing fourseven:scss.
It's throwing the error at the fsevents install
Failed at the [email protected] install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the fsevents package,
npm ERR! not with npm itself.
See if this helps: https://github.com/meteor/meteor/issues/7568
Dogfalo
on 7 Feb 2017
I have the same issue on windows 7
masza
on 7 Feb 2017
@Dogfalo I think fsevents is a osx thing. We're not using osx. Is there any way for us to not use that with your package?
I tried installing node-pre-gyp to global. Meteor just released a patch too and I installed that. I removed bcrypt like someone suggested in that thread and it's still giving me the same issue.
I'm just going to have to use the static files you guys provided for now.
muffinrecon
on 7 Feb 2017
Yes the problem, as I already pointed out, is very likely to be fsevents that is an OSX stuff and we're on Windows
NitroBAY
on 7 Feb 2017
Yeah i know the issue here. I also had I it once. I fixed it by removing materialize and fourseven and meteor reset.
tomscholz
on 9 Feb 2017
@tomscholz I tried to install materialize on a fresh Meteor project and the installation didn't work though
NitroBAY
on 9 Feb 2017
Strange 🤔
On Feb 9, 2017 12:09, Ilan Schemoul notifications@github.com wrote:
@tomscholzhttps://github.com/tomscholz I tried to install materialize on a fresh Meteor project and the installation didn't work though
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Dogfalo/materialize/issues/4193#issuecomment-278612287, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATcANbbHPLK2nX7z_-QKV16YdyBp1mEGks5ravO6gaJpZM4L4XXD.
tomscholz
on 9 Feb 2017
Hi @Dogfalo ,@acburst
Will there be a patch to resolve this issue on window soon?
Thanks
haojia321
on 12 Feb 2017
Hi @nitroBAY
Have you found a way to resolve this issue?
haojia321
on 14 Feb 2017
@j1016h @NitroBAY It works for me on Windows 10 Pro 64bit. I am not able to reproduce the problem...
Have you tried this?: npm install -g node-gyp node-pre-gyp
or just to update node?
tomscholz
on 14 Feb 2017
Try to install fourseven:scss=3.9.0 first before you materialize. It worked on my machine. Don't forget to specify the version.
runners4tme
on 14 Feb 2017
@j1016h yes I downloaded the repo, put it in the package then meteor add materialize:materialize works.
NitroBAY
on 14 Feb 2017
@tomscholz I'm pretty sure I did, anyway as everything's working with the local repo I'll wait before trying your fix
NitroBAY
on 14 Feb 2017
@NitroBAY Could you tell me more detail about your fix please?
What repo did you download? Where did you put it in?
It will be a great help if I can resolve it.
haojia321
on 14 Feb 2017
@j1016h Dude ^^. Just clone the materialize repo into a folder in the root of your project called packages/
tomscholz
on 14 Feb 2017
@tomscholz I dont see any folder called packages... Is it inside somewhere under .meteor folder?
haojia321
on 14 Feb 2017
No, you have to create it.
- Create a folder called "packages" in the root of your project
- CD into that folder and run git clone https://github.com/Dogfalo/materialize.git
On Feb 14, 2017 20:22, Hao Jia notifications@github.com wrote:
@tomscholzhttps://github.com/tomscholz I dont see any folder called packages... Is it inside somewhere under .meteor folder?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Dogfalo/materialize/issues/4193#issuecomment-279807565, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATcANe5rAFUx-n5O7TXq60sVZjhxukUIks5rcf7dgaJpZM4L4XXD.
tomscholz
on 14 Feb 2017
@tomscholz I got below error when start meteor
While processing files with fourseven:scss (for target web.browser):
/packages/materialize_materialize/sass/materialize.scss: Scss compiler error: File to import:
{materialize:materialize}/sass/components/tapTarget not found in file:
D:/hao/test/{materialize:materialize}/sass/materialize.scss
haojia321
on 14 Feb 2017
Ok Ok thats ok. All you have to do now is to switch to the v0.98.0 tag.
You can achieve this by running this inside your materialize folder, that is located here: /path/to/yourproject/packages/materialize:
git fetch --tags
git checkout v0.98.0
I don't know if you are familiar with sass, but the error appears because inside the materialize.scss (located here), the tapTarget.scss file is requested, but it isn't loaded by meteor in the package.js
tomscholz
on 14 Feb 2017
Awesome! It works now.
Thanks @tomscholz
Summary:
- Create a folder called "packages" in the root of your project
- CD into that folder and run git clone https://github.com/Dogfalo/materialize.git
- CD into materialize and run git fetch --tags
- In same folder, run git checkout v0.98.0
haojia321
on 14 Feb 2017
This works but there is a problem with the fonts. Any idea?
Ots parsing error: invalid version tag...Failed to decode dowloaded font
danteblink
on 22 Feb 2017
It seems, that fsevents is a dependant of another dependencie
tomscholz
on 22 Feb 2017
@danteblink Can you post the content of the package.js that is inside your local materialize folder?
tomscholz
on 25 Feb 2017
I tried on a fresh project npm install -g node-gyp node-pre-gyp it didn't fix materialize.
BUT meteor add fourseven:scss@=3.9.0 did the trick.
NitroBAY
on 26 Feb 2017
But fourseven:scss 3.9.0 doesn't work with new Meteor versions nor with Materialize ($medium-and-down not found, Meteor 1.4.1 requires fourseven 4.5.0 etc)
NitroBAY
on 26 Feb 2017
I have the same problem with empty project.
torendo
on 12 Mar 2017
Is this still an issue? It works for me on Windows 10 and Mac Os 11.11.
tomscholz
on 28 Apr 2017
@tomscholz Yes, it is still an issue.
I tested on a new windows 10 laptop with a fresh installed Meteor 1.5.
I created a new project and see the isssue while run meteor add materialize:materialize
Log (Click to expand)
Error:
While loading materialize:[email protected]...:
error: Command failed:
C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\bin\npm.cmd Loading matrebuild --update-binary98.... \
node-pre-gyp ERR! Tried to download(404):
https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.15/fse-v1.0.15-node-v46-win32-ia32.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and [email protected] (node-v46 ABI) (falling back to
source compile with node-gyp)
Traceback (most recent call last):
Filee: meteor create [--release <release>] [--bare|--full] <path> Loading materialize:[email protected].... \"C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\gyp\gyp_main.py", --list
line 16, in <module> --package [<package_name>]
sys.exit(gyp.script_main())[email protected].... \
File a subdirectory named <path> if it doesn't exist and create a new Meteor app
"C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\gyp\pylib\gyp\__init__.py",on to create Loading materialize:[email protected].... -
line 545, in script_main
return main(sys.argv[1:])
File the --package option, creates a Meteor package instead of an app. If you're Loading materialize:materialize"C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\gyp\pylib\gyp\__init__.py",n the current dire
line 538, in main
return gyp_main(args)materialize:[email protected].... -e --release
Fileon, or the latest available version if the option is not specified. (A
"C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\gyp\pylib\gyp\__init__.py",utside a meteor app will Loading materialize:[email protected].... -
line 523, in gyp_main
generator.GenerateOutput(flat_list, targets, data, params) Meteor
Filele applications. Use --list to see the available examples. There are Loading materialize"C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py",
line 2021, in GenerateOutput
sln_projects, project_objects, flat=msvs_version.FlatSolution()). /
Fileexample Example template to use.
"C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py", Loading materialize:[email protected].... /
line 1780, in _GatherSolutionFolders.
return _DictsToFolders('', root, flat)
File Loading"C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py",
line 1733, in _DictsToFolders
for folder, contents in bucket.iteritems():g materialize:[email protected].... /
AttributeError: 'MSVSProject' object has no attribute 'iteritems'
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1 Loading materialize:[email protected] ERR! stack at ChildProcess.onCpExitearning resources here:
(C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\lib\configure.js:336:16)
gyp ERR! stack at emitTwo (events.js:87:13)|
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:12)
gyp ERR! System Windows_NT 10.0.15063 Loading materialize:[email protected].... |
gyp ERR! command
"C:\\Users\\h1016\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.5.0\\mt-os.windows.x86_32\\dev_bundle\\bin\\node.exe" Loading materialize:materia"C:\\Users\\h1016\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.5.0\\mt-os.windows.x86_32\\dev_bundle\\lib\\node_modules\\node-gyp\\bin\\node-gyp.js"
"configure" "--fallback-to-build"
"--module=C:\\Users\\h1016\\AppData\\Local\\Temp\\mt-15tidv0\\npm\\node_modules\\.temp-1fwa53g\\node_modules\\fsevents\\lib\\binding\\Release\\node-v46-win32-ia32\\fse.node"
"--module_name=fse" teor --help'.
"--module_path=C:\\Users\\h1016\\AppData\\Local\\Temp\\mt-15tidv0\\npm\\node_modules\\.temp-1fwa53g\\node_modules\\fsevents\\lib\\binding\\Release\\node-v46-win32-ia32"
gyp ERR! cwd C:\Users\h1016\AppData\Local\Temp\mt-15tidv0\npm\node_modules\.temp-1fwa53g\node_modules\fsevents
gyp ERR! node -v v4.8.3 Loading materiagyp ERR! node-gyp -v v3.6.0\
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute:[email protected].... \
'C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\bin\node.exe
C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\bin\node-gyp.jspp. Loading materialize:[email protected].... \
configure --fallback-to-build
--module=C:\Users\h1016\AppData\Local\Temp\mt-15tidv0\npm\node_modules\.temp-1fwa53g\node_modules\fsevents\lib\binding\Release\node-v46-win32-ia32\fse.node [email protected].... \
--module_path=C:\Users\h1016\AppData\Local\Temp\mt-15tidv0\npm\node_modules\.temp-1fwa53g\node_modules\fsevents\lib\binding\Release\node-v46-win32-ia32'
(1) Loading materialize:[email protected].... -
node-pre-gyp ERR! stack at ChildProcess.<anonymous>
(C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
node-pre-gyp ERR! stack at emitTwo (events.js:87:13)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:172:7)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:862:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:222:5)
node-pre-gyp ERR! System Windows_NT 10.0.15063
node-pre-gyp ERR! command
"C:\\Users\\h1016\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.5.0\\mt-os.windows.x86_32\\dev_bundle\\bin\\node.exe"
"C:\\Users\\h1016\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.5.0\\mt-os.windows.x86_32\\dev_bundle\\lib\\node_modules\\node-pre-gyp\\bin\\node-pre-gyp"
"install" "--fallback-to-build"
node-pre-gyp ERR! cwd
C:\Users\h1016\AppData\Local\Temp\mt-15tidv0\npm\node_modules\.temp-1fwa53g\node_modules\fsevents
node-pre-gyp ERR! node -v v4.8.3
node-pre-gyp ERR! node-pre-gyp -v v0.6.34
node-pre-gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install 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\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\.npm\_logs\2017-06-11T16_02_39_813Z-debug.log
node-pre-gyp ERR! Tried to download(404):
https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.15/fse-v1.0.15-node-v46-win32-ia32.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and [email protected] (node-v46 ABI) (falling back to
source compile with node-gyp)
Traceback (most recent call last):
File
"C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\gyp\gyp_main.py",
line 16, in <module>
sys.exit(gyp.script_main())
File
"C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\gyp\pylib\gyp\__init__.py",
line 545, in script_main
return main(sys.argv[1:])
File
"C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\gyp\pylib\gyp\__init__.py",
line 538, in main
return gyp_main(args)
File
"C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\gyp\pylib\gyp\__init__.py",
line 523, in gyp_main
generator.GenerateOutput(flat_list, targets, data, params)
File
"C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py",
line 2021, in GenerateOutput
sln_projects, project_objects, flat=msvs_version.FlatSolution())
File
"C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py",
line 1780, in _GatherSolutionFolders
return _DictsToFolders('', root, flat)
File
"C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py",
line 1733, in _DictsToFolders
for folder, contents in bucket.iteritems():
AttributeError: 'MSVSProject' object has no attribute 'iteritems'
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit
(C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\lib\configure.js:336:16)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:12)
gyp ERR! System Windows_NT 10.0.15063
gyp ERR! command
"C:\\Users\\h1016\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.5.0\\mt-os.windows.x86_32\\dev_bundle\\bin\\node.exe"
"C:\\Users\\h1016\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.5.0\\mt-os.windows.x86_32\\dev_bundle\\lib\\node_modules\\node-gyp\\bin\\node-gyp.js"
"configure" "--fallback-to-build"
"--module=C:\\Users\\h1016\\AppData\\Local\\Temp\\mt-15tidv0\\npm\\node_modules\\.temp-1fwa53g\\node_modules\\fsevents\\lib\\binding\\Release\\node-v46-win32-ia32\\fse.node"
"--module_name=fse"
"--module_path=C:\\Users\\h1016\\AppData\\Local\\Temp\\mt-15tidv0\\npm\\node_modules\\.temp-1fwa53g\\node_modules\\fsevents\\lib\\binding\\Release\\node-v46-win32-ia32"
gyp ERR! cwd C:\Users\h1016\AppData\Local\Temp\mt-15tidv0\npm\node_modules\.temp-1fwa53g\node_modules\fsevents
gyp ERR! node -v v4.8.3
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute
'C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\bin\node.exe
C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-gyp\bin\node-gyp.js
configure --fallback-to-build
--module=C:\Users\h1016\AppData\Local\Temp\mt-15tidv0\npm\node_modules\.temp-1fwa53g\node_modules\fsevents\lib\binding\Release\node-v46-win32-ia32\fse.node
--module_name=fse
--module_path=C:\Users\h1016\AppData\Local\Temp\mt-15tidv0\npm\node_modules\.temp-1fwa53g\node_modules\fsevents\lib\binding\Release\node-v46-win32-ia32'
(1)
node-pre-gyp ERR! stack at ChildProcess.<anonymous>
(C:\Users\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.windows.x86_32\dev_bundle\lib\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
node-pre-gyp ERR! stack at emitTwo (events.js:87:13)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:172:7)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:862:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:222:5)
node-pre-gyp ERR! System Windows_NT 10.0.15063
node-pre-gyp ERR! command
"C:\\Users\\h1016\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.5.0\\mt-os.windows.x86_32\\dev_bundle\\bin\\node.exe"
"C:\\Users\\h1016\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.5.0\\mt-os.windows.x86_32\\dev_bundle\\lib\\node_modules\\node-pre-gyp\\bin\\node-pre-gyp"
"install" "--fallback-to-build"
node-pre-gyp ERR! cwd
C:\Users\h1016\AppData\Local\Temp\mt-15tidv0\npm\node_modules\.temp-1fwa53g\node_modules\fsevents
node-pre-gyp ERR! node -v v4.8.3
node-pre-gyp ERR! node-pre-gyp -v v0.6.34
node-pre-gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install 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:
D:\test>
D:\test>\h1016\AppData\Local\.meteor\packages\meteor-tool\1.5.0\mt-os.window
D:\test>13Z-debug.log
Work around from my previous comments will work but we want to know if it can be fixed in package itself?
haojia321
on 11 Jun 2017
@meteor @stubailo @benjamn @abernix Do you have any idea or a suggestion how we can solve this problem?
tomscholz
on 11 Jun 2017
@tomscholz The problem here is with fsevents trying to be installed on a Windows platform (It's an OS X-only package). This seems to indicate that materialize:materialize or one of its dependencies has been published from a directory where the node_modules directory included the fsevents package, thus it has been included in the package bundle.
This is along the same lines as https://github.com/moment/moment/pull/3538 (and the linked/related issues).
This is merely a suggestion (since it's mentioned frequently above), but is it possible that at one point this happened with the fourseven:scss package? The dependency in materialize:materialize is on an old version of that package and it has seen a lot of updates!
abernix
on 12 Jun 2017
@abernix That means, when we publish the atmosphere pakage, we should only have the production dependencies installed? fsevents is a dependency of one of our devDependencies (Browsersync)
tomscholz
on 12 Jun 2017
@tomscholz Correct. Since files in node_modules are import-able by packages, they are included when running meteor publish and anything listed in devDependencies is installed within node_modules–devDependencies are useful for packages too sometimes!
If there are packages which you will not need in production, you should remove them from the node_modules directory prior to publishing. You can do this on an existing node_modules by running meteor npm prune --production.
abernix
on 12 Jun 2017
@abernix And using Ok! Thanks :)Npm.depend would not exclude all unneeded packages?
tomscholz
on 12 Jun 2017
on an old version of that package and it has seen a lot of updates!
@abernix So it would also make sense to change this line to just api.use('fourseven:scss'); ?
tomscholz
on 12 Jun 2017
@tomscholz Yup, as long as you don't have a dependency on a specific version of fourseven:scss! That would allow apps to use newer versions of fourseven:scss, which has seen a _lot_ of updates from it's team!
abernix
on 13 Jun 2017
@abernix Ok, but one more thing. Do we need this line https://github.com/Dogfalo/materialize/blob/master/package.js#L16? I am not that familiar with meteor. Is something like this making more sense?
tomscholz
on 13 Jun 2017
@tomscholz You only need to use.imply a package if you want the consumers of _your_ package to have access to that package as well. For example, with this line, if someone installs materialize:materializethey will have access to the $ (and jQuery) variables in their application, even if they do not explicitly add the jquery dependency to their package themselves.
So, only set api.imply('jquery') if you want to give users jQuery if they use Materialize. If you just want to use jquery in materialize:materialize, then you only need api.use('jquery'). If you also don't need jQuery, then you can remove jquery altogether. :)
Hope this helps! More here in the docs, hopefully: https://docs.meteor.com/api/packagejs.html#PackageAPI-imply
abernix
on 13 Jun 2017
Should be fixed in the latest version. Can anyone confirm? Otherwise I would close this issue now.
tomscholz
on 22 Jun 2017
Closed due inactivity. Feel free to reopen, if it's still necessary.
tomscholz
on 27 Jun 2017
Okay. I have serious problems using Materialize with my meteor project.
I can't seem to get this to work no matter what on my Windows 10 machine.
It was working before I updated meteor... now everything is broken.
I have tried to clone materialize and revert to v0.98.0, but this causes constraints issues with fourseven:scss.
While selecting package versions:
error: Conflict: Constraint fourseven:[email protected] is not satisfied by
fourseven:scss 0.9.6.
Constraints on package "fourseven:scss":
fourseven:[email protected] <- materialize:materialize 0.98.0
DDews
on 22 Nov 2017
Hello everyone, I guess same problem. Trying to install Materialize on meteor.
First installed fourseven 4.5.4 : meteor add fourseven:scss
And then trying to install Materialize : meteor add materialize:materialize
Node version: 4.8.4
npm version: 2.15.11
Here is the error logs: https://pastebin.com/wdhiAyW3
Oyshoboy
on 26 Nov 2017
I was able to reproduce the problem on Windows 10 and the work around https://github.com/Dogfalo/materialize/issues/4193#issuecomment-279825788 corrected my issue.
I did not execute the _meteor add fourseven:scss_ command.
Thanks
php-bob
on 23 Mar 2018
Related issues
SoproniOli713
·
3Comments
alexknipfer
·
3Comments
samybob1
·
3Comments
serkandurusoy
·
3Comments
heshamelmasry77
·
3Comments
Most helpful comment
Awesome! It works now.
Thanks @tomscholz
Summary: