webpack 3 compatibility

[FranckFreiburger]

Is url-loader@1.1.1 really not compatible any more with webpack 3 ? (like suggested in the package file
https://github.com/webpack-contrib/url-loader/blob/v1.1.1/package.json#L42) ?

[michael-ciniawsky]

It is compatible, the peerDependency is just wrong/unneeded. In my opinion it should simply be relaxed, but there doesn't seem to be consensus to make this change (see #142)

[michael-ciniawsky]

Just ignore the warning

[FranckFreiburger]

ok thanks !

[alexander-akait]

@michael-ciniawsky can we close issue?

[afgrant]

Since it's a change that breaks backward compatibility, shouldn't requiring a semver major increment in peerDependencies trigger a semver major increment here? The same would apply to dropping support for a version of node in the engines. To update from 1.0.x to 1.x.x and lose webpack@3 compatibility is a semver contradiction.

The simplest way out is to release:

• 1.1.2 with webpack@3 || webpack@4 and consider 1.1.x EOL, which looks like the case already
• 2.0.0 with webpack@4