saiichihashimoto / react-router-html-webpack-plugin Goto Github PK

To resolve #14 and to resolve #15, we need to hook into the compilation process. Basically:

• Webpack needs to run its loaders on the routes configuration
• Webpack needs to load the routes config and use react-router-to-array to get the routes
• Webpack needs to create an instance of html-webpack-plugin for each route

For the first two to happen, what do we do? A child compiler? Putting things into the proper step in the process? Will it have to do all this to the routes before the usual entry points or in parallel?

Currently, the routes are simply being required directly, which is a poor experience. They need to go through webpack's system so it goes through the loaders, THEN we can grab the routes and use them.

When loading the routes, react-router-html-webpack-plugin doesn't use webpack at all. It simply dumps its results into webpack. It needs to work within webpack watch mode as well, which implies that we need webpack to watch routes, recompile it on change, and run through the remaining steps.

Linked to #14