An example of code splitting with next, redux and custom redux-dynamic-modules.
Manipulate your store like an egg tray. Add some eggs to your Redux store.
Contents:
Here is a monorepository that contains packages that allow you to easily split your Redux store into separate
parts (eggs), and then dynamically add and remove them when you need it. This set of packages will allow you to reduce
the size of your Redux store and the first-load JavaScript by adding only the currently needed reducers and middlewares.
You no longer have to add all reducers and middlewares at once when creating your Redux store. If you need some kind of
reducer or middleware, you can dynamically add these constructs at runtime exactly when your application requires it.
You will be able to create reusable constructs with reducers and middlewares so that you can easily connect them in
different parts of your application. Moreover, if you need reusable parts of the Redux store in different projects, you
can also create separate reusable packages and use them in your projects.
If you are familiar with Redux Dynamic Modules, then most likely
you know what is going on here.
@redux-eggs/core - a package that includes the main logic for adding and removing parts of Redux store, connecting
extensions, triggering events, etc.
@redux-eggs/next - Redux Eggs wrapper for Next.js.
@redux-eggs/react - a package that provides higher-order component (HOC) and function to create an injector
component that allows you to add parts of Redux store before the component is mounted,
and remove them after the component is unmounted.
@redux-eggs/redux - a wrapper for directly creating dynamic Redux store with plain Redux.
@redux-eggs/redux-toolkit - a wrapper for directly creating dynamic Redux store
with Redux Toolkit.
@redux-eggs/saga-extension - an extension for Redux Eggs that allows you to dynamically add or
remove sagas from your Redux store.
