Maël Nison

It's not only a question of position. Let's say you have this package.json: ```js { "dependencies": { "a": "^1.0.0" }, "devDependencies": { "b": "^1.0.0" } } ``` And that the...

Now that I think about this, maybe in practice it could work, since the lockfile would still pin the version - at least assuming that this lockfile has been generated...

Not a fan. You shouldn't call the script in the first place, or should use `|| true` to silence errors if you need it.

I don't think `yarn unlink package` is meant to trigger an install (or at least, I'd feel uncomfortable changing this behavior anywhere else than in a major release). In the...

> These are only actionable when you are adding or upgrading packages. I suspect a fair amount of our users never use `add` and `remove`, and instead manually update their...

> "when running install but only if package.json is updated (doesn't match yarn.lock)" Looks correct. > Even yarn project itself has this: warning "[email protected]" has incorrect peer dependency "ajv@>=4.10.0". This...

An extra thing I think that we could/should do (in the process of improving the publish process) would be to have an actual validation. It shouldn't be possible to push...

> Hi @ishiijp, as mentioned above, it appears that Yarn has decided to not publish new versions in the npm registry, which is where Volta gets its information. Update: I've...

Your case is expected, @royra. Use `|| true` to silence the error if matching nothing is the intended behaviour. > May I ask what is the reasoning behind the new...

Shells tend to have different behaviours. For instance zsh does throw on zero-match glob patterns. At least now we guarantee that the behaviour will be consistent by default, and you...