Peer dependency issue for elm 0.19.1-1 about elm-webpack-loader HOT 8 CLOSED

I don't. Tried out a couple of things but didn't have much luck :/

from elm-webpack-loader.

@Skinney Any idea why ^0.19.1-0 || 0.19.0-no-deps doesn't seem to match 0.19.1 according to https://semver.npmjs.com/ (while ^0.19.0-0 || 0.19.0-no-deps does seem to match 0.19.0)?

from elm-webpack-loader.

Guess we'll have to look upstream 😞

from elm-webpack-loader.

I ended up ditching webpack for a custom Elm buildpack (we're on Heroku) and Parcel. Was a rough few days not being able to deploy.

from elm-webpack-loader.

@heyakyra I think it makes sense to ^0.19.1-0 || 0.19.0-no-deps. At least then we get the latest 0.19.1 release.

from elm-webpack-loader.

This issue gave me a reason give Parcel a try. Turned out the switch was quite easy. I find Parcel much easier to use than Webpack. I am not going back to Webpack :-)

from elm-webpack-loader.

This seems to work for me when I DONT have elm as a peer dependency and instead have it installed on the CLI, does that make any sense?

I get this warning

npm WARN [email protected] requires a peer of [email protected] || ^0.19.1 but none is installed. You must install peer dependencies yourself.

But it still compiles fine?

from elm-webpack-loader.

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.

from elm-webpack-loader.