Clement Yan
Clement Yan
> If the focus install would require the lockfile to be updated... A focused install, almost by definition, would require the lockfile to be updated. A focused install literally *mutates*...
As noted, this is an issue with Yarn Classic. The Yarn Modern equivalent `yarn config set cacheFolder true` does not lead to an error.
Yarn does not enforce provenance of peer dependencies. (Neither does npm, not sure about pnpm). You cannot specify *where* a package comes from, only that the parent can resolve the...
This is one of the fundamental limitations of `node_modules` resolution -- without using the `--preserve-symlinks` flag it is impossible to correctly resolve peer dependencies across symlinked dependencies (e.g. workspace) Say...
@BaidenGenie Not related. For one, you are using yarn v1. And, the error message looks nothing like the one in the OP. If you are still encountering problems please open...
All versions of `@microsoft/kiota-abstractions` on the npm registry are prerelease versions, which [normally doesn't satisfy `*`](https://github.com/npm/node-semver/blob/145c554b8c7b7ecfcb451153ad18bdb2f24ad10d/README.md#prerelease-tags). Looks like pnpm just treat `*` as a synonym of `latest` https://github.com/pnpm/pnpm/blob/eeb76cd1d0a3133d71d96de5646e305f34474652/resolving/npm-resolver/src/pickPackageFromMeta.ts#L148-L152 Maybe we...
> I think it'd make sense to tolerate the prerelease versions until at least one stable is released. We can't make `*` tolerate all prerelease everytime though, it wouldn't match...
@zZHorizonZz You can use [resolutions](https://yarnpkg.com/configuration/manifest#resolutions) to bypass the default resolution algorithm, e.g.: ```json "resolutions": { "@microsoft/kiota-abstractions": "npm:latest" }, ```
As I have said in https://github.com/yarnpkg/berry/issues/6329#issuecomment-2184931696, the problem with this approach is that the flag is simply ignored in `yarn explain peer-requirements --warnings p00000` and that can be confusing. I...
The `yarn up ` command only updates the listed packages. See the [examples](https://yarnpkg.com/cli/up#examples) in the documentation. If you want to update *all* packages, you want `yarn up -R '*'`