Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heroku deployment fails on fsevents #411

Closed
rich-ware opened this issue Apr 19, 2014 · 5 comments
Closed

Heroku deployment fails on fsevents #411

rich-ware opened this issue Apr 19, 2014 · 5 comments

Comments

@rich-ware
Copy link

I am having a tough time getting my first meanio app running on Heroku. I have only created the app & tried to deploy to Heroku.
I followed deployment steps at https://github.com/linnovate/mean/wiki/Deploying-on-Heroku .

Here is the error log:

8133 info fsevents@0.2.0 Failed to exec install script
8134 error fsevents@0.2.0 install: node-gyp rebuild
8134 error Exit status 1
8135 error Failed at the fsevents@0.2.0 install script.
8135 error This is most likely a problem with the fsevents package,
8135 error not with npm itself.
8135 error Tell the author that this fails on your system:
8135 error node-gyp rebuild
8135 error You can get their info via:
8135 error npm owner ls fsevents
8135 error There is likely additional logging output above.
8136 error System Linux 3.8.11-ec2
8137 error command "/tmp/build_458a9f3a-3430-4b0a-9b37-e93c00567a1d/vendor/node/bin/node" "/tmp/build_458a9f3a-3430-4b0a-9b37-e93c00567a1d/vendor/node/bin/npm" "rebuild"
8138 error cwd /tmp/build_458a9f3a-3430-4b0a-9b37-e93c00567a1d
8139 error node -v v0.10.26
8140 error npm -v 1.4.3
8141 error code ELIFECYCLE
8142 verbose exit [ 1, true ]

! Push rejected, failed to compile Node.js app

Please advise on how to resolve. Also, let me know if you need more information.

Thanks!

@wmbutler
Copy link

wmbutler commented May 1, 2014

Same issue here.

@fyockm
Copy link
Contributor

fyockm commented May 1, 2014

@rich-ware @wmbutler are you running an up-to-date version of mean? I know a lot of modules were moved from devDependencies into dependencies and that helped a number of others with heroku deployment.

Also, please see here.

@wmbutler
Copy link

wmbutler commented May 1, 2014

I solved this by removing karma:

sudo npm uninstall karma

On Thu, May 1, 2014 at 12:57 PM, Drew Fyock notifications@github.comwrote:

@rich-ware https://github.com/rich-ware @wmbutlerhttps://github.com/wmbutlerare you running an up-to-date version of mean? I know a lot of modules were
moved from devDependencies into dependencies and that helped a number of
others with heroku deployment.

Also, please see herehttps://github.com/linnovate/mean#heroku-quick-deployment
.


Reply to this email directly or view it on GitHubhttps://github.com//issues/411#issuecomment-41936219
.

Bill Butler
bill@butler.net
(615) 330-5044

@lambtron
Copy link

lambtron commented Aug 2, 2014

I'm having the same issue.

Trying to deploy wintersmith onto Heroku. One of wintersmith's dependency is fsevent, which is giving me the same output logs as OP.

I believe fsevent is the offender here. Any ideas?

@andreaskern
Copy link

Wintersmith depends on chokidar which optionally depends on fsevents. fsevents only gets installed on MacOS as a workaround for node.js's file module. it actually fails to install on ubuntu and is ignored.

'npm rebuild' still tries to build fsevents if present and fails although it's optional.

i hope that helps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants