xervoio / docker-run-meteor Goto Github PK

Since nvm is packaged with the bundle, it grabs the package.json from the $NVM_DIR. Need to be specific to the findFile function to look in ./bundle

Issue originally opened on the modulus-cli by @victorlambert

Hi guys,

I'm trying the new modulus cli and meteor runtime.
Deployment is running fine but I get this error when starting the app (from the logs) :

Now using node v0.10.41
Found package.json: ./.modulus/nvm/package.json
WARNING: Main file not specified in package.json.
WARNING: Looking for common main file names: index.js, app.js, server.js, main.js.
ERROR: No main or start script found. There is no application to run.

I do have a start script in my package.json :

...
  "scripts": {
    "start": "meteor --settings settings-development.json",
...

Any idea ?
Thanks for the great work

EDIT :
After downgrading to 5.0.1 and 5.0.0 I get the same error ... everything was working fine before I tried the new cli/runtime. Need to deploy today, hope I will find the issue.

We are having an urgent problem with our deploys – they don’t go through.
Our URLs are sirenioreefbox.mod.bz and sirenio.com http://sirenio.com/ and we’re getting exit code 0 although it doesn’t seem to pass.

This is the response we are getting (when deploying to either one of them):

Demeteorizing application...
/mnt/home/.meteor/packages/meteor-tool/.1.3.3_1.tnlp4e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/meteor-promise/promise_server.js:165
throw error;
^
undefined
Conversion failed.
Build attempt failed, attempting again.

We tried deploying with different versions and on different systems – no cigar.
Last time we had troubles deploying we were advised to upgrade the Modulus CLI, so downgrading again doesn't seem like a good solution. Please advise.

Some users are reporting issues where dependencies that are included in a root package.json are not available at runtime.

Reference: XervoIO/cli#141