"There is no route for the path: /" in production bundling

when i’m building for production flowrouter gives a “There is no route for the path: /” In development mode all is working as expected.

running:

• meteor 1.4.1
• deployment with mup
• Webapp build with React

currently testing the bug with;

meteor run --production --settings settings-production.json

Try to solve it with;

1. change the routes.js file location to /import/clients/routes.js
2. change between mup/mupx and new mup deployment…
3. change to flowrouter ServerSideRendering
4. check for any Ready()

If anyone found a solution for the “There is no route for the path: /” in production bundling. That would be great.

[saulflores95]

Hey @grinono thank you for responding, I was able to get it working. I had materialize meteor packet and mui design packet (this one was installed via npm) that I removed. After i did a clean cache of my meteor npm_modules folder. I reinstalled all my npm packets with --save(Except the two that I previously removed). When I uploaded the app to the server everything was working.

Hope this helps someone.

[dmattbergstrom]

Hi!

I didn’t find the solution for this problem by anything here, but after 8 hours of hacking, i solved it.

1. Some packages didn’t work in production for me, in Meteor 1.8. Check all your non-core packages and try to remove them one by one and see if that fixes the issue.

I removed the following problematic packages: aldeed:autoform gwendall:auth-client-callbacks dsyko-jquery-ui-touch

1. Useraccounts was not included on both server and client. The page using that package was included in my routes.js file, and therefore mucked up all my routes, resulting in this nasty bug.

---

My tip for anyone who needs to figure out their own way of solving this bug:

1. Start commenting out packages in .meteor/packages.json while running your app in the terminal with the production tag activated. That means, run your app with the following command, while removing possibly outdated packages (usually non-standard ones)

“meteor run --production”

1. Keep the app running in production mode. Start commenting out routes in your routes.js file, and see if you can find the route/page that is mucking up all routes and causing this error.

Good luck! / Devmattb