Upgrading to babel 5.5.1 breaks configuration about babel-loader HOT 7 CLOSED

Does it work fine if you use the babel cli?

from babel-loader.

It does run, but I can't test it fully with the cli as the code depends on more webpack specific loaders.

from babel-loader.

Using the require hook from babel in my tests, seems to work though.

from babel-loader.

Ok! Thanks for the tests.
I'll try to replicate your problem as soon as I can (which means when I get out of work).

Also out of curiosity, and kinda like a shot in the dark, can you try the new loader version? (5.1.4)
It fixes an unrelated issue, but the timeline of both issues is the same, so I'm just throwing ideas until I get to fix your issue.

from babel-loader.

Thanks for the quick reply. I did some more debugging and this is what I found:

• 5.1.4 no changes in behaviour.
• Logging opts in https://github.com/babel/babel/blob/master/src/babel/transformation/transformer-pipeline.js#L70 does not show the .babelrc options (they are not presented in any of the babel-loader code either, but I expected that as babel should load them?)

from babel-loader.

• Hard coding the options in the webpack configuration makes them show up in the above mentioned places, but they still seem to not have any effect :(

from babel-loader.

Fixed as of Babel 5.5.4, thanks! :)

from babel-loader.