No compatability with autoExport
See original GitHub issueWith https://github.com/zeit/next.js/issues/7355 coming into Next.js, many applications will move to use this feature for the obvious performance benefits.
Unfortunately, for this to work, getInitialProps
cannot be altered at the client level of a page.
https://github.com/kirill-konshin/next-redux-wrapper/blob/master/packages/wrapper/src/index.tsx#L46
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Automated Drupal 10 compatibility fixes [#3296835] | Drupal.org
Problem/Motivation Hello project maintainers, This is an automated issue to help make this module compatible with Drupal 10. To read more about this...
Read more >2022 PDF Compatibility Settings in Export - CreativePro Network
What's the general rule of thumb for PDF compatibility when exporting? ... If no information is forthcoming, I export to PDF/X-4:2008, ...
Read more >Health Auto Export - JSON+CSV on the App Store
View and export data from iPhone on Mac and iPad; Export Workouts and Health data to JSON, CSV and GPX files; enjoy Health...
Read more >Profile does not export to GPK using Export to Native ...
When running the General Geometry>Export to Native (or Auto Export in the Feature Definition), the selected profile does export to the GPK.
Read more >Export Apple Health Data - JSON & CSV - Health Auto Export
How to Export Apple Health Data? Use Health Auto Export! Automatically Export Apple Health Data to CSV | Automate Apple Health data exports...
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
Good point. I will update readme now.
After looking at this issue more I am confused even more. The main purpose of this library is to make sure some actions are consistently dispatched on all pages on client and on server. It uses
getInitialProps
for that.Like I said before, previous version of the lib was working on page level. But honestly, I don’t think it’s a good idea to use redux wrapper on some pages as you would need to take care that no redux-connected component will appear on a page that was not wrapped. So rule of thumb always was to wrap all pages. Which is exactly what the new version does.
Which brings us to conclusion:
If you need a static website you don’t need this lib at all because you can always dispatch at client side and let server only serve initial/static markup.