"There is no route for the path: /" in production bundling
See original GitHub issuewhen 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;
- change the routes.js file location to /import/clients/routes.js
- change between mup/mupx and new mup deployment…
- change to flowrouter ServerSideRendering
- 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.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7
Top Results From Across the Web
There is no route for path '/' on production
I am using flowrouter + react + meteor. I don't have any errors in development. But when i host or simulate production, then...
Read more >Prefix Error in Production | Symfony 5 | No route found
Probably you are misusing the routing rules. Prefixes (and paths) are single-valued parameters. Multiple values are accepted only on in case ...
Read more >Migrating to React Router v6: A complete guide
Migrate your React Router applications from v5 to v6 with this in-depth guide, including a review of additions and improvements from v5.
Read more >Routes - Networking | OpenShift Container Platform 3.11
A path to a directory that contains a file named tls.crt. If tls.crt is not a PEM file which also contains a private...
Read more >Fixing the 'cannot GET /URL' error on refresh with React ...
The root of the issue is that you're relying entirely on client side routing without setting up any logic to handle server-side routing....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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.
Hi!
I didn’t find the solution for this problem by anything here, but after 8 hours of hacking, i solved it.
I removed the following problematic packages: aldeed:autoform gwendall:auth-client-callbacks dsyko-jquery-ui-touch
My tip for anyone who needs to figure out their own way of solving this bug:
“meteor run --production”
Good luck! / Devmattb