[bug?] Unexpected "There is no route for the path: /" errors in console
See original GitHub issueProblem Description
I have a route that works with the following definition at the bottom of a jsx file:
FlowRouter.route("/", {
subscriptions: function(params, queryParams) {
// if(queryParams && queryParams.email){
// this.register('runwayEventsForEmail', Meteor.subscribe('runwayEvents', queryParams.email));
// }
},
action: function(params, queryParams) {
ReactLayout.render(ReactChanApp);
}
});
ReactChanApp
renders as expected, but I keep getting errors from utils.js
saying the route is missing, e.g: There is no route for the path: /
DEMO
https://github.com/raibutera/flow-router-185
npm install && cd app && meteor
Issue Analytics
- State:
- Created 8 years ago
- Comments:14 (3 by maintainers)
Top Results From Across the Web
Error : There is no route for the path: / · Issue #608 - GitHub
I have updated Meteor to Meteor 1.3.2.4. and facing the issue. Error : There is no route for the path: / I tried...
Read more >Angular2 routing, using TypeScript, has a compile error and ...
First, your route is broken @RouteConfig( [ {path: '/home', as: component: Home } ] ). You need to define the alias and make...
Read more >Node.js Handling invalid routes - GeeksforGeeks
While developing Node.Js application it is important to handle invalid routes. It can be done by writing a custom route or redirecting all ......
Read more >errorElement v6.6.1 - React Router
When a route does not have an errorElement , errors will bubble up through ... the error in the console, so removing it...
Read more >VNC Connect Error Messages - RealVNC Help Center
VNC Viewer may display the following error messages if a connection ... a warning that xauth was not on the PATH and indicated...
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 FreeTop 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
Top GitHub Comments
Experiencing this since migration to 1.4.1 and react-mounter and react 15
Any chance of adjusting this so that I can use the npm react package rather than the atmosphere one?