allow ol-dev-versions as peer dependency

[RobertOrthofer]

Following the convention of ol-mapbox-style, this should allow projects to use the very latest dev-versions of ol, which could include critical features.

[m-mohr]

Hmm, this doesn't indicate which the minimum version of ol is required though, so not ideal. Is there an alternative?

[RobertOrthofer]

This is true, generally these can be found in the README, unfortunately I am not aware of an alternative.

I have to admit that this not ideal, I hope there is a real solution for this issue from the side of npm in the near future. For now this is a judgment call about what is more important, knowing the minimum version when looking into the package.json-file, or allowing to use the latest features and fixes from ol.

Personally, i think that very few users will use this package alongside a legacy version of ol <7.5.2, while having to use the dev-Version because of some critical new feature/fix is quite common.

[ahocevar]

@m-mohr Other 3rd party libraries for ol do the same, and I'm doing it also in ol-mapbox-style. Of course there's a trade-off between having the minimum compatible version in package.json and convenience of working with dev versions of OpenLayers, but after talking to @tschaub about his experiences I decided to go with "*".

[m-mohr]

Alright. @RobertOrthofer Could you please add the minimum required version to the README instead?

[RobertOrthofer]

@m-mohr I have added it to the README and made a small FAQ entry, if that's ok

[m-mohr]

Thanks, the CI is failing though. Seems like an issue with the package-lock.json

[m-mohr]

Thanks, merged.