Peer dependency issue for elm 0.19.1-1

Elm 0.19.1 is out. Installing elm@latest (=elm 0.19.1-1) causes elm-webpack-loader to report:

npm WARN elm-webpack-loader@6.0.0 requires a peer of elm@0.19.0-no-deps || ^0.19.1 but none is installed. You must install peer dependencies yourself.

Alternative: run npm upgrade. But, that tries to install elm@0.19.1 (without the -1). This throws an error in the install script:

    throw new errors.TypeError('ERR_INVALID_ARG_TYPE', 'path', 'string');
    ^

I’m stuck. Seems to me elm-webpack-loader (still?) has a dependency issue?

[robinheghan]

I don’t. Tried out a couple of things but didn’t have much luck 😕

[robinheghan]

Sure. A peer dependency should only give you a warning that you need to install something yourself. We don’t actually depend on elm being installed by npm, just that it exists. Us definining it as a peer dependency is just a way of telling our users that it should be of a certain version, but we’ll try running it anyways.