Better messaging about ^

[hzoo]

Ref #6795
Ref #6804

Also I was just thinking that npm install eslint which also automatically uses ^. Just brainstorming, but I think we can maybe add a warning somehow (maybe after install) about using ~ instead of ^?

Most users will still be surprised since they won't see the README/semver policy (mostly for our sake since we'll probably get a lot of reports unless users know about it)

[nzakas]

I don't know -- I feel like that's ESlint being a bit too opinionated. Maybe people won't read the docs, but we can always point them to it. I'm not sure we need more than that.

[hzoo]

Yeah hard to say. Was just exploring what we can do to inform since I think we'll get reports about it whenever there is something like that - given its the default.

It's not in the best spot (or on the website) so even skimming through it you might not see it (or even the semver policy really).

[nzakas]

I'm definitely 👎 on having ESLint check what your package.json says when it's running -- some may still want to use ^ and I don't want to nag them about it.

Do you have another recommendation?

[ljharb]

Is it entirely out of the question to change the semver policy in such a way as more things cause semver-major bumps? There's zero things wrong with being on v123.4.5 if it comes to that.

[nzakas]

@ljharb we just formalized the policy, so I don't think it's worthwhile to investigate changing it again. We already had a bunch of discussion around it and there's no new information that I could see leading to a different result.

[ljharb]

Gotcha, just wanted to throw that one out there.

[alberto]

@ljharb actually there is an issue with plugins compatibility.

[ljharb]

@alberto sure, the issue is that plugins would have to release more aggressively.

[nzakas]

Unfortunately, it looks like consensus couldn't be reached on this issue and so I'm closing it. While we wish we'd be able to accommodate everyone's requests, we do need to prioritize. We've found that issues failing to reach consensus after 21 days tend never to reach consensus, and as such, we close those issues. This doesn't mean the idea isn't interesting, just that it's not something the team can commit to.