Maël Nison
Maël Nison
Yep, multiple repetitions of the `-c` flag sound good to me 👍
Just stumbled upon this issue. The lead problem is in `@types/react-dom`. Short answer is that by defining `@types/react` as a *dependency* (rather than a *peerDependency*), `@types/react-dom` is exposing itself to...
> so unless developers use the peer dependency field correctly we keep having this issue and the only workaround is by using That unfortunately won't solve the issue (at least...
> does it mean that yarn is supporting the "resolutions" field in package.json ? Is this documented somewhere ? Well yes, we kinda invented it 😄 Regarding the initial issue...
Yarn creates a temporary directory each time a script is executed, in order to setup "fake" Node and "fake" Yarn binaries that point towards the exact same Yarn/Node than those...
There is no risk removing those files when Yarn isn't running. Even when running, it should be relatively safe as they're usually only used when the program boots. Fwiw this...
> Just for clarification (even if it will hurt), I guess this means version 1.x will not receive a fix, but 2.x has the issue fixed? In this case the...
You probably have an invalid lockfile or npmrc.
It yields new errors :( Would someone have some time to check this out?
As @kohlikohl noted, Yarn always tries to resolve from the registry when the version is missing (it tries to find the latest one and use it). If someone is willing...