-
Notifications
You must be signed in to change notification settings - Fork 27k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[examples/with-redux-wrapper] doesn't work with "next-redux-wrapper": "7.0.2" #26338
Comments
Hello, I'd like to take this as my first next.js contribution |
Hey, The way I tried reproducing the error and 3rd step from migration steps solved it for me-
@timneutkens should I update the example with-redux-wrapper with the latest changes in |
Fixed with #26521 |
## Bug - [x] Related issues linked using `fixes #number`: Fixes #26338 - [ ] Integration tests added
## Bug - [x] Related issues linked using `fixes #number`: Fixes vercel#26338 - [ ] Integration tests added
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
What example does this report relate to?
with-redux-wrapper
What version of Next.js are you using?
11.0.0
What version of Node.js are you using?
14.16.1
What browser are you using?
Google Chrome
What operating system are you using?
Linux Ubuntu 18.04
How are you deploying your application?
Vercel
Describe the Bug
From the directory
examples/with-redux
, I installed the latest version available ofnext-redux-wrapper
, 7.0.2, as I begin to use it in my main project. After npm installation step, I launch the examplenpm run dev
.Compilation seems to work, but as soon as I look at the page through google chrome, I got the following error:
Expected Behavior
I expect to be able to see the example page. The example works correctly with previous version of
next-redux-wrapper
, 6.0.2To Reproduce
From
examples/with-redux-wrapper
directory, updatenext-redux-wrapper
:Launch the example:
Look at the page in a browser.
The text was updated successfully, but these errors were encountered: