Webpack integration

[TheTFo]

Hello,

Is there a recommended way to integrate this with a webpack build? Otherwise, would this be a good candidate for a plugin?

Thanks!

[oliviertassinari]

@TheTFo Why do you need to integrate with a webpack build? We use it at @doctolib on 3k+ modules bundled with webpack, without webpack. Have you seen the example?

[TheTFo]

It would be cool to have it run on every change, so that the strings are extracted as I save, via webpack-dev-server.

On Fri, Feb 10, 2017, 2:43 AM Olivier Tassinari [email protected] wrote:

@TheTFo https://github.com/TheTFo Why do you need to integrate with a webpack build? We use it at @doctolib https://github.com/doctolib one 3k modules + bundled with webpack, without webpack. Have you seen the example https://github.com/oliviertassinari/i18n-extract/blob/master/examples/polyglot.js ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/oliviertassinari/i18n-extract/issues/26#issuecomment-278878517, or mute the thread https://github.com/notifications/unsubscribe-auth/AAgWoHtAfJSQWWLo8tXs3cpPdF9kb4fOks5rbBU0gaJpZM4L86Ci .

[leebenson]

This totally makes sense as a Webpack plugin. In my ReactQL starter kit, I have a comprehensive Webpack config that builds multiple bundles for both Node and the browser, and hot reloads on development.

Every Webpack plugin currently performs some kind of syntax validation - e.g. if PostCSS throws an error due to a missing semi-colon in a .css file, that error feeds through to both the console and the hot-reloaded browser.

Having errors report back through this common interface without running separate linting scripts would be awesome.