yann-combarnous

@Bnaya , to be on-par with CRA4 when it comes to webpack dev server logging, could you consider adding ``` stats: 'errors-warnings' ``` to webpack.config.json? This will get rid of...

> There was an open issue in the Istanbul plugin that was recently fixed for this... can you give this a try @lucaspeterson22 [iFaxity/vite-plugin-istanbul#13](https://github.com/iFaxity/vite-plugin-istanbul/issues/13)? Unfortunately, ´all: true’ option for nyc...

My workaround is to disable chunk-splitting in Vite using: ``` { rollupOptions: { output: { manualChunks: () => 'bundle', } } ``` Otherwise with code splitting, Vite only parses the...

> I have created a vite [plugin](https://github.com/Dunqing/vite-plugin-react-esbuild) for this purpose. > > I made some changes, removed `restoreJSX` and adjusted the execution order, now esbuild->react plugin. > > Now it...

Any blocker on this PR?

Trying to follow PR progress, anybody could shed light on what is still missing? Thx for the great work!

Excited to see this one coming together. Thx to all for your work!

@raix , could this be added to 5.0.1, by any chance? It would reduce CRA verbosity on startup.

> **Folks on 6.4+ but not using a Data Router** > > If you've upgraded to 6.4+ but aren't using a data router, then you can also still use `unstable_HistoryRouter`...

> Ah - thanks for calling this out - that's a new 6.4-only thing. Does everything work fine if you ignore that with `// @ts-expect-error`? That `encodeLocation` method is new...