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

Reinstall fibers. #16

Open
webeng opened this issue Jun 12, 2013 · 6 comments
Open

Reinstall fibers. #16

webeng opened this issue Jun 12, 2013 · 6 comments

Comments

@webeng
Copy link

webeng commented Jun 12, 2013

Hello,
I am using your builpack meteorite for deploying a telescope project to heroku. I always get this error.
"/app/.meteor/heroku_build/app/server/node_modules/fibers/fibers.js:13
2013-06-12T11:37:23.986034+00:00 app[web.1]: throw new Error(''+ modPath+ '.node is missing. Try reinstalling `node-fibe
2013-06-12T11:37:23.988931+00:00 app[web.1]: at Module._compile (module.js:456:26)
"

It seems it's a problem with fibers. Do you know why is this happening?
Thanks

@kevinharvey
Copy link

I had the same problem, and I think it's a Fibers 1.0.0 vs. 1.0.1 issue. I couldn't get Fibers to reinstall, but on a fresh install I pinned Fibers in package.json and got past this.

{
  ...
  dependencies: {
    "fibers": "1.0.1"
  }
}

@saulshanabrook
Copy link

@kcharvey Could you post your full package.json, because I am still having this error. I don't think it is installing fibers for some reason.

@saulshanabrook
Copy link

For the record, when I my package.json depends on fiber version 1.0.0 or 1.0.1

{
  "name": "myapp",
  "version": "0.0.1",
  "dependencies": {
    "fibers": "1.0.0"
  }
}

It will crash like this:

2013-07-12T16:10:27+00:00 heroku[slug-compiler]: Slug compilation finished
2013-07-12T16:10:32.555970+00:00 heroku[web.1]: Starting process with command `.meteor/heroku_build/bin/node .meteor/heroku_build/app/main.js`
2013-07-12T16:10:33.316479+00:00 app[web.1]: Add phantomjs/casperjs paths ...
2013-07-12T16:10:34.395238+00:00 app[web.1]: /app/.meteor/heroku_build/app/server/server.js:337
2013-07-12T16:10:34.398100+00:00 app[web.1]:     at Array.forEach (native)
2013-07-12T16:10:34.394494+00:00 app[web.1]:
2013-07-12T16:10:34.395496+00:00 app[web.1]:   }).run();
2013-07-12T16:10:34.395496+00:00 app[web.1]:      ^
2013-07-12T16:10:34.398100+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/server/server.js:298:12
2013-07-12T16:10:34.398100+00:00 app[web.1]:     at app/casperjs/config.js:1:28
2013-07-12T16:10:34.398100+00:00 app[web.1]: ReferenceError: require is not defined
2013-07-12T16:10:34.398100+00:00 app[web.1]:     at Function._.each._.forEach (/app/.meteor/heroku_build/app/server/node_modules/underscore/underscore.js:78:11)
2013-07-12T16:10:34.398100+00:00 app[web.1]:     at run (/app/.meteor/heroku_build/app/server/server.js:239:7)
2013-07-12T16:10:35.668379+00:00 heroku[web.1]: Process exited with status 1
2013-07-12T16:10:35.682515+00:00 heroku[web.1]: State changed from starting to crashed

@saulshanabrook
Copy link

My error was because I had other javascript in folders in my repo that meteor was trying to run. Prefixing those with a . fixed the errors.

@gowlin
Copy link

gowlin commented Oct 11, 2013

I'm having this original error about reinstalling fibre as well. I added a package.json to my meteor application in the top level directory, but that doesn't seme to solve the problem still. Are there any other work around options for this?

@lucasfeliciano
Copy link

In which folder do you put the package.json?

Can some one post a entire package.json as exemple for the telescope application?

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

5 participants