Epic: Separate entry point for Dashboards #5426
Description
Background
Splitting the application into different entry points with different bundles will allow us to clean up our redux store, and also allow different teams to have different approaches to state management without affecting the rest of the app.
Considerations
This diagram details the top of the application that among other things, fetches the data the app needs from the API and store it in state. If you'd like the link to the Miro diagram this image was taken from, reach out to Bucky.
Off the top of my head, I can't think of any section of the application that won't need some of the data fetched by the above component tree. This makes it a very good candidate as a dependency that every entry point can depend on, which is a property of the entry point object in Webpack. What we'll do is create an entry point for that data and have every other entry point depend on it.
Acceptance Criteria
- Create an entry point for dashboards
- Create an entry for the top of the application (the parts detailed in the above screenshot) that other entry points can depend on (may not be possible without webpack 5)