Mark Stacey
Mark Stacey
>I didn’t even know they were strictly mandatory. Well.... they're intended to support plugins, which is a situation in which the peer is required. *A lot* of people use them...
> I think the best feature would be to rework the logging to assign codes + data to the various warnings, and allow our users to select which ones then...
That all seems pretty reasonable! Going forward, I suppose `yarnrc` should be preferred for new project configuration over `package.json`? It seems safer to add things to `yarnrc` - less likely...
I have a couple more questions. ``` ignore-warnings: missing-peer-dependency: - name: typescript expected-by: ts-node ``` That format looks pretty good, but it is missing the version range. Including the range...
This discussion is a bit fractured ([here](https://github.com/yarnpkg/yarn/issues/3330), [here](https://github.com/yarnpkg/yarn/issues/5892), [here](https://github.com/yarnpkg/rfcs/pull/84), and [here](https://github.com/yarnpkg/yarn/issues/5891)), so I've attempted to summarize my interpretation of it here. ## Purpose of the `resolved` field As far as...
After further consideration, adopting the behavior of npm v5 might be a breaking change after all (as mentioned [here](https://github.com/yarnpkg/rfcs/pull/84#discussion_r146956291)). What I had in mind was for Yarn to do as...
>For non-scoped packages, it never was supported in the first place (after all the lockfile has a big "DO NOT EDIT" notice at the very top) and I don't think...
> it would be better for the next release to be the 2.0, ideally. Well, that's exciting! That leaves us with little time to update these RFCs. I've just put...
After tracing the install process taken by Yarn, it looks like it does use that field as a cache. I can't see how it would construct it without asking the...
I've done a bit more investigation on the option of generating the tarball URL using the standard format (`${registry}${packageNameWithScope}/-/${packageNameWithoutScope}-${packageVersion}.tgz`). It looks like this approach was taken by `pnpm`, but it...