Josh David

@jaredpalmer when you get a chance to review 🙏 Wasn't sure if you preferred caret versions (`^`) or greater than (`>=`) to avoid this issue for future major version updates.

Now that cypress v7 is out, I updated this to a `>=` check to ensure the new version is included, and any future versions. @jaredpalmer when you get a chance.

@raunaq1990 did you mean to use `run-p` instead of `npm-p`? https://github.com/mysticatea/npm-run-all/blob/master/docs/run-p.md

I believe there is one remaining issue, and that is with `reduceHook` (in `packages/yarnpkg-core/sources/Configuration.ts`) which was previously using the first parameter of hooks as an initial value and passing each...

> This is a breaking change for npm versions that lack optional peer dep support. Hi @ljharb. I'm not sure I understand why this would be a breaking npm

This change doesn't add the dependencies to `peerDependencies` though, so there shouldn't be any impact there. They're only added to `peerDependenciesMeta` as optional. So packages that do not support `peerDependenciesMeta`...

If marking a dependency as optional in `peerDependenciesMeta` it implicitly considers that to be `"dependency": "*"` if no specific version ranges have been listed in `peerDependencies`. So it seems like...

Yep I am running PnP in CI for now and node modules linker locally. The node modules linker in both yarn and npm seem to work in this case as...

`eslint-plugin-import` isn't the only consumer of `eslint-module-utils` though. There are other plugins like https://github.com/azz/eslint-plugin-monorepo which use the utils to resolve paths. If you're saying that these packages too should add...

npm may have been grandfathered into node, but I wouldn't say it is the "standard". Node now provides yarn and pnpm out of the box via corepack. I still don't...