Promise Error when creating route to a container
See original GitHub issueI’m new to react and I decide to use this boilerplate for my first project. I don’t know if this is a bug or if I need to link some things manually, but when I create a container and a route to this new container with the generator, I get an error when I try to access this container.
The error is the following:
es6.promise.js:119 Unhandled promise rejection ReferenceError: injectAsyncReducer is not defined
Issue Analytics
- State:
- Created 7 years ago
- Comments:38 (18 by maintainers)
Top Results From Across the Web
Error "Error: A <Route> is only ever to be used as the child of ...
The error message is pretty clear, wrap your Route components in a Routes component. The routes also don't take children (other than other...
Read more >CannotPullContainer task errors - Amazon Elastic Container ...
The common cause for this error is because the VPC your task is using doesn't have a route to pull the container image...
Read more >Initialization of sharing external failed ... - GitHub
It changes to another error: app.js:62 Uncaught (in promise) ReferenceError: app2 is not defined while loading "./routes" from webpack/container/reference/ ...
Read more >4 Reasons Why Your Docker Containers Can't Talk to Each ...
After you finally containerise your Node.js app, you're eager to see if it works. You run it, but then this happens: "Error: connect...
Read more >Let It Crash: Best Practices for Handling Node.js Errors on ...
An unhandledRejection error is a newer concept. It is emitted when a promise is not satisfied; in other words, a promise was rejected...
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

@ralomucho What do you mean by changing the default selector? (I’m getting the same error as @jamesmbowler)
Edit: Nevermind, I figured it out. A simple way to remove the error would be to do this:
Double edit: Perhaps a good default for the template would be something like this instead? This way the errors won’t show up when nothing has changed.