tsarapke

Have tried to create "proj2 (https://github.com/tsarapke/proj2.git)" with Webpack 5 avoiding `react-scripts`. So yes, it could not find workerized chunk. It throws 404 error.  So... is it actually a bug...

Regarding first point, as far as I know, at the moment some work is being done towards migration (have no idea how long it would be). As for the second......

Any chance(plans) to get it fixed in near future? This actually blocks a case when lib and project does not depends on `react-scripts`. So you can't make it work with...

@alexander-akait there is already provided case by @dandansoysauce. In a few word, if I have library with WebWorker and some application that builded with Webpack 5 but not with RCA,...

You can read my first message in this topic > Adding new Worker construction in library, produces additional chunk in build result (what is quite expected). How I can make...

What if the source code of the library should be closed to its users? For third-party developers who are planning to build their system based on the library?

@markerikson Unfortunately no, it doesn't. It solves the issue with type of `const store`, so it doesn't of `any` type anymore. But `RootState` still circularly references itself. 

@phryneas It also doesn't help. At reproduction link, I've already specify return type of slice. V1:  V2 

@phryneas There are **only 2** slices, created by the **same creator**  Slice at row 6 is fine. Slice at row 7 is not. But they are created by the...

`fetchImage2` rely on `RootState`. `fetchImage2` is async thunk where we want to use `getState`.  `ImageState` doesn't rely on `RootState`. `ImageState` is a part of `RootState`.