Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[0.1.0] Unmet peer dependency error where none is missing

See original GitHub issue

I ran:

npm i @fortawesome/fontawesome-svg-core@prerelease \
      @fortawesome/free-solid-svg-icons@prerelease \
      @fortawesome/vue-fontawesome@prerelease

npm yields:

npm WARN @fortawesome/vue-fontawesome@0.1.0-4 requires a peer of @fortawesome/fontawesome-svg-core@>= 1.2.0 < 1.3 but none is installed. You must install peer dependencies yourself.

Excerpt from package.json:

"dependencies": {
    "@fortawesome/fontawesome-svg-core": "1.2.0-14",
    "@fortawesome/free-solid-svg-icons": "5.1.0-11",
    "@fortawesome/vue-fontawesome": "0.1.0-4",
    ...
}

Might be related to #60.

Issue Analytics

State:
Created 5 years ago
Comments:9 (8 by maintainers)

Top GitHub Comments

1reaction

robmadolecommented, Jun 27, 2018

We don’t have a future pre-release yet. However, I don’t think we’re going to use ranges with prerelease versions any longer (they just are not predictable between tools). So the underlying issue for this won’t be an issue in the future.

1reaction

robmadolecommented, May 18, 2018

Yeah we probably need to change this. We chose the current scheme based on https://semver.org/#spec-item-9. I wonder if our issues could be considered a bug in the semver package.