webpack@2 introduced a breaking change between beta22 & beta23

[MoOx]

Basically all configuration for eslint-loader, postcss-loader, sass-loader need to be moved out of webpack config as it's validated AND THROW ERRORS. Well... Fuck semver.

• Use JSON schema to validate webpack config (fixes #2971) webpack/webpack#2974
• beta23 doesn't start if config object includes loader configs because of schema webpack/webpack#3018

"Official" solution is to move those options into a loader plugin call...

webpack/webpack#2974 (comment)

You can say "no big deal man". But seriously, all of this because in the first place query can't handle some real JS (in a js file, that's funny right?)

This solution is not acceptable for me with my current mood as everybody will have to update more of their code. So I am not ready to cut a release with this dawn change and it's blocking us for a major release. I am pissed off, sorry for that.

Tell me what you think about the "official" solution (it's more a poor "workaround" to me)...

[DavidWells]

[MoOx]

Ok this has not been clear but it seems that query accept any JS now. This will do the trick.
Also what will need to be done:

• remove makeConfig (webpack 2 support directly a function)
• replace "loaders" by "rules"
• replace custom key by query directly

[thangngoc89]

Oh craps. This release takes forever.

[MoOx]

This release takes forever.

This is for the better ;)

[thangngoc89]

replace "loaders" by "rules"

What is this?

[MoOx]

just renaming "loaders" by "rules" in webpack.module section ( so module.loaders => modules.rules)

[thangngoc89]

I like that changes. It's confused as hell when I worked on the loader configuration transformer

[MoOx]

Fixed (kind of) in 7ca3cb1