Allow customizing loaders with webpack

[goatslacker]

Maybe if there is a webpack.config.js already present then use that instead?

[goatslacker]

The use case:

someone is using import 'foo.css' in there react module, now this won't work with reactview.

[zackify]

Actually does work, I added the css loader, but I see your point. Good
idea.
On Sat, May 16, 2015 at 13:56 Josh Perez notifications@github.com wrote:

The use case:

someone is using import 'foo.css' in there react module, now this won't
work with reactview.

—
Reply to this email directly or view it on GitHub
#4 (comment).

[zackify]

At that point, you might as well just use the webpack dev server don't you think? Maybe just pull in loaders from their config and that's it?

[goatslacker]

that could work

[RJ]

doesn't quite work for me out of the box, i think because of extra features i've enabled with babel. reusing existing webpack config file makes sense imo.

[zackify]

Can you post your config? I'm using stage 0 transforms already.
On Mon, May 18, 2015 at 04:15 Richard Jones notifications@github.com
wrote:

doesn't quite work for me out of the box, i think because of extra
features i've enabled with babel. reusing existing webpack config file
makes sense imo.

—
Reply to this email directly or view it on GitHub
#4 (comment).

[RJ]

ah, i think it's because all my files are .js not .jsx, and your webpack requires jsx extension

[zackify]

Yes thanks I will fix that today!
On Mon, May 18, 2015 at 08:18 Richard Jones notifications@github.com
wrote:

ah, i think it's because all my files are .js not .jsx, and your webpack
requires jsx extension

—
Reply to this email directly or view it on GitHub
#4 (comment).

[zackify]

@RJ: @gaearon just pushed a fix for that, will publish to npm shortly. As for this issue, should I just hijack the loaders section of the webpack config?

[zackify]

Should add this issues to https://github.com/insin/react-heatpack, I'm deprecating this project.