Meteor 1.3 app works locally but is broken after deploy #141
Comments
|
+1 Having this exact same problem |
|
Also an issue for me - different files but the same problem. With 'react' - it deploys the app and then cannot find 'react' when running on modulus. Works fine locally. e.g. Same notice about npm install - but that change nothing (and it works fine locally). Meteor 1.3.2.4 |
|
Did you try the suggestion from the error message? |
|
@fiveisprime of course, remember that the app works perfectly locally, so the packages are there. The only difference I can see between meteor build locally and modulus is the architecture, since Im using osx. |
|
Sorry accidentally closed the issue |
|
@fiveisprime Yes, the issue is that error message is showing up from the build, which is occurring on the Modulus machine. So even if you wanted to run that command, you don't have access to the Modulus server to do so. And like @monvillalon , those errors are not showing up locally, and the correct npm_modules are loaded as you would expect. |
|
It's failing to build on the server because those packages aren't saved for your project's config. You don't need to run those commands on the server, you need to run them before deploying so it's all saved, right? The The project will run locally just like a node project would if you ran |
|
@fiveisprime If I understand you correctly you are saying that this might be caused by not having the relevant packages on package.json. But they are there. |
|
What's your project ID? |
|
What is also weird is that two days before it worked. |
|
Same here - all of those modules are saved in my package.json. |
|
@fiveisprime I have since deleted the app, and moved it to another provider since this was a time sensitive issue. I will recreate the app later today and will put the id here. |
|
My app ID is Pairprep. I also switched hosting providers this weekend due to this issue, but I'm redeploying now to Modulus and seeing the same issue. |
|
I too have tried all the suggestions from the error message - including completely removing node_modules and running 'npm install' again (fyi: that means it looks at package.json and downloads all the listed files again to recreate node_modules). The local build continues to work without issue. I also downloaded Demeteorizer, ran it manually, created a bundle and it ran perfectly fine locally. I then attempted to zip up the demeteorized version of the app and deploy it as a NodeJS application (I created another project from scratch). That had too many different errors (I suspect that is why Modulus created the MeteorJS container to cater for differences in Meteor 1.3). @fiveisprime - you reset one of my projects for me that was stuck uploading [neither project has this problem set of build files now but I can attempt to deploy again if it will be of any assistance - which will be about another 8-9 hours away before I can attempt this; as at posting]. I am in a similar situation to @monvillalon - I need to keep moving forward and can't really be bogged down dealing with hosting issues (if I were going to do that, I'd build my own VM from the ground up). So, I am going to have to look at other alternatives if this can't be resolved soon. In my case, the project was last successfully deployed 7 days before this issue occurred and worked fine then. |
|
+1 ... same problems with meteor@1.4+ |
|
I did not redeploy. I was requested by my client to look into other hosting (which immediately worked without issue). I am somewhat disappointed because Modulus looked like a very good option for a startup but it's Meteor.... so (price notwithstanding) there's a fairly clear "pain free" choice which only took an hour to run up and confirm and another hour to create an alternative MongoDB account, grab a DB backup, and restore (good exercise to do before launching into Production). CLOSED - from my perspective. |
|
About to switch over to MDG's Galaxy myself...there seems to disappointingly be a new issue with modulus every single time there is an update to either node or meteor. |
|
I've created a new issue specifically targeting missing dependencies on the To everyone who is experiencing issues, we understand your frustration and are trying our best to resolve the situation. We want everyone to be able to run the newest version(s), but we need to maintain compatibility for those with apps running older versions as well. Meteor 1.3.x and 1.4.x have been especially difficult in that regard. |
I have a meteor 1.3 that runs perfectly locally by either
meteor runormeteor buildbut when deploying to modulus withmodulus deploydemeteorizer warns that "Unable to resolve some modules:", after a successful deploy react the error I'm seeing is that react is not found.My versions are:
meteor 1.3.4.1
modulus-cli 6.1.1
node v6.3.0
npm 3.10.7
Relevant output:
The text was updated successfully, but these errors were encountered: