Bump loader-utils and use getOptions

[existentialism]

Fixes warning:

DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.

Ref: webpack/loader-utils#56

[danez]

This breaks as the new loader-utils version drops support for node < 4

[codecov]

Codecov Report

Merging #391 into 7.0 will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##              7.0     #391   +/-   ##
=======================================
  Coverage   81.87%   81.87%           
=======================================
  Files           6        6           
  Lines         160      160           
  Branches       35       35           
=======================================
  Hits          131      131           
  Misses         13       13           
  Partials       16       16

Impacted Files	Coverage Δ
src/index.js	82.85% <100%> (ø)	✅

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a483384...77e63e6. Read the comment docs.

[Timer]

Considering that Node 4 is the oldest supported version of Node (0.10 and 0.12 being dead), one could argue it's not a breaking change.

[kaumac]

+1
this will hopefully fix #392

[gaearon]

Can we release babel-loader@7 without waiting for Babel 7? Doesn't seem like they have to track each other.

[Nilegfx]

+1

[joshwiens]

@danez - Nothing related to Webpack 2.x supports node < 4. Agree with @Timer, I wouldn't consider this breaking as support for .10 / .12 was never there to begin with as support was dropped when NodeJS officially dropped their support of these versions.

Webpack will continue to drop support for versions as NodeJS does

This has been handled as a patch version for all loaders requiring the same change across the webpack-contrib org.

[hassox]

I've been trying to get a new project up and this issue is so far very difficult to solve. This plugin is now at odds with most other loaders and loaderUtils does not support parseQuery anymore :( I'd love to see this (or something similar) get merged in soon :D

[mrtnbroder]

Please release this asap, it's causing issues on our app.

[blade254353074]

...We are waiting for this release

[danez]

The deprecation warning is now fixed in v7.0.0-alpha.2

[mgol]

@danez loader-utils is still tested in Node 4: https://github.com/webpack/loader-utils/blob/master/.travis.yml so it seems they should support it?

[danez]

but not for node <4

[mgol]

Ah, sorry, I read it incorrectly.

[corysimmons]

Been through a couple walls of text. Using Node 7.4.0 with latest webpack and babel-loader. Still getting this error. Can someone summarize what's wrong and what needs to be done?

[Timer]

@corysimmons if you're using latest of babel-loader, that's your problem. You need to be on next.

If you are on next (v7), go ahead and run node with the --trace-deprecation flag to figure out exactly where the deprecation is coming from.

[corysimmons]

yarn add -D babel-loader@next?

[Timer]

Yup, if you want to be more explicit @7.0.0-beta.1

[corysimmons]

Thanks, works. 👍

[Vanuan]

Does babel-loader@next work with babel-core 6?

[danez]

@Vanuan Yes babel-loader does work with babel-core 6.x