Break with using thread-loader on production about jsxstyle

[meyer]

@Sunshine168 hmm, that’s interesting. Investigating…

[meyer]

Looks like thread-loader two major limitations that make compatibility with jsxstyle-webpack-plugin a bit challenging:

• Loaders cannot emit files.
• Loaders cannot use custom loader API (i. e. by plugins).

jsxstyle-webpack-plugin is first and foremost a plugin, which means that the companion loader cannot be used without the context object that the plugin provides to each loader instance. In addition, the loader emits a CSS file for each JS file that it runs on as well.

It should theoretically be possible to have a loader-only version of jsxstyle-webpack-plugin, but this is not something I’d be able to achieve in the near future. If you’re looking to reduced build/rebuild times, jsxstyle-webpack-plugin’s companion loader works quite well with cache-loader.

Sorry I couldn’t give you better news. Do let me know if you have any additional questions.