You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I have a codebase recently upgraded to 1.3. However, all deployment fails with a message in the lines of:
Error: Can't find npm module 'body-parser'. Did you forget to call 'Npm.depends' in package.js within the 'iron_router' package?
I rhc ssh to the machine, and try to manually install the required npm module which goes well. However, upon next start, I get the same error but with a different module and package. That goes on and on, and I suspect either package compatibility or the build process itself from Meteor to Node app.
Another thing worth mentioning is that if I create a new 1.3 app, build and deploy, it works. I didn't add packages to it, and the application itself doesn't have legacy code.
This might very well be unrelated to the Openshift deployment as people have had it in Modulus, Mup, DigitalOcean instances and more, but if there's someone who knows how to fix it I'd appreciate it.
The text was updated successfully, but these errors were encountered:
Apparently, the solution is to do: git config --system core.longpaths true if you're running Windows, since not all node modules will get committed to Git, because of the 260 character limit.
Hi. I have a codebase recently upgraded to 1.3. However, all deployment fails with a message in the lines of:
I
rhc ssh
to the machine, and try to manually install the required npm module which goes well. However, upon next start, I get the same error but with a different module and package. That goes on and on, and I suspect either package compatibility or thebuild
process itself from Meteor to Node app.Another thing worth mentioning is that if I create a new 1.3 app, build and deploy, it works. I didn't add packages to it, and the application itself doesn't have legacy code.
This might very well be unrelated to the Openshift deployment as people have had it in Modulus, Mup, DigitalOcean instances and more, but if there's someone who knows how to fix it I'd appreciate it.
The text was updated successfully, but these errors were encountered: