Bug: npm 7 peer vue dep about vue-gtm HOT 9 CLOSED

ok, I agree

from vue-gtm.

Could you create a simple minimal reproduction repo that I can checkout/clone?
Maybe it's just changing the peer dependency from ^3.0.0 to >=3.0.0 <4.0.0 🤔, but I'm not sure
Does it work with yarn or other tools? Does it work with npm 6?

from vue-gtm.

Could you create a simple minimal reproduction repo that I can checkout/clone?
Maybe it's just changing the peer dependency from ^3.0.0 to >=3.0.0 <4.0.0 🤔, but I'm not sure
Does it work with yarn or other tools? Does it work with npm 6?

npm 6 ok, this problem only in npm 7 maybe use ">=3.0.0 || ^3.0.0-beta"

from vue-gtm.

So I checked via this site: https://jubianchi.github.io/semver-check/#/^3.0.0/3.1.0-beta.3
that the peer dependency is configured right and that ^3.0.0 also satisfies 3.1.0-beta.3

So I don't what I need to do here 😕

But maybe it's an issue with how vue / vue-router handles its versions, cause these are on a "next" channel and not "latest"

But yes, like I'm getting now e.g. a warning like this when I set vue-router in devDependencies to 4.0.8:

warning package.json: "optionalDependencies" has dependency "vue-router" with range "^4.0.0" that collides with a dependency in "devDependencies" of the same name with version "^4.0.8"

from vue-gtm.

ok @Shinigami92 see please https://semver.npmjs.com/

you

and my ^3 || ^3.0.0-alpha || ^3.1.0-alpha

from vue-gtm.

Okay we need to find a version range that includes everything between >=3.* and <4 🤔
I don't want to specify for every beta version a 3.X...-alpha

So I don't want to maintain something like ^3 || ^3.0.0-alpha || ^3.1.0-alpha || ^3.2.0-alpha || ^3.3.0-alpha || ^3.4.0-alpha ... beyond to infinity ...

How do I do that?

from vue-gtm.

Beside that, I'm not sure if I "want" to support a beta version 🤔
I mean, yeah it works, but I will not deliver support if there is something broken based on a beta version
Just when it will release officially, I will update an fix the breaking

from vue-gtm.

@Shinigami92

1. Definitely due instead of >=3.* and <4 use ^3
2. Support only last beta releases ^3.1.0-alpha It is unlikely that someone needs old beta, and about support - update lazily :)

final result: ^3 || ^3.1.0-alpha

from vue-gtm.

Cause I cannot find a way to specify all beta versions with just one easy range, I'm sorry, but I think I will not support beta versions for now.

If you are using beta versions you are an early adopter and there can be errors with that.

Setting it explicitly in my package.json means I officially support these non-production ready versions.

Also it's not only vue, but also vue-router that could get a beta...

So I would currently need something like

vue: ^3.0.0-a || ^3.1.0-a || ^3.2.0-a ...
vue-router: ^4.0.0-a || ^4.1.0-a || ^4.2.0-a ...

Sorry, but I don't want to create a release just due to there is a new beta release 🙁

If I understand correctly using --legacy-peer-deps is the correct workaround for now, isn't it? That's cause you rely on a beta version.

from vue-gtm.