"Unable to resolve package" when package/version exists

[andrewfulrich]

I'm trying to move some examples over to stackblitz but ran into this error installing @bayer/ol-kit

Reproduction steps:

• add ol@4.6.5 to dependencies to see that installs just fine by itself
• add @bayer/ol-kit to dependencies to see the error message

This looks similar to #286 and #175
but I don't see any malformations in the package.json at https://github.com/MonsantoCo/ol-kit/blob/v0.2.2/package.json

Why would it look for ol@~4.0 when the dependency in the package.json specifies ol@4.6.5? Wouldn't it at least look for ol@~4.6?

[EricSimons]

Hm, do any subdependencies of @bayer/ol-kit specify ol@~4.6? That's the most likely culprit. I can investigate this deeper but any additional info would be super helpful so I can get to the bottom of it quicker

[andrewfulrich]

You're right, ol@~4.0 a dependency of @terrestris/ol-util@0.5.0 which is a dependency of geostyler-openlayers-parser@0.21.0. When I install it locally, it does npm WARN that this is an unmet peer dependency:

but it works fine locally despite the warning, since the peer dependency of ol-kit itself is ol@4.6.5 and that gets installed. Is there any way for Stackblitz to ignore peer dependency warnings?

[kc0tlh]

@andrewfulrich, sorry for the delayed response! This issue should be resolved in our new VS Code editor! If it doesn't work out of the box, try this command: npm install --legacy-peer-deps and let us know!