Paul Berg
Paul Berg
This new dependency model should come with the ability to separate development dependencies from production dependencies. At the moment, when Foundry installs a repo, it pulls all testing-related dependencies of...
> Perhaps it would be reasonable to just adopt using https://github.com/foundry-rs/forge-std/pull/322? [Pnpm](https://pnpm.io/) and yes, I agree :D
> Fixed in https://github.com/OpenZeppelin/openzeppelin-contracts/pull/4261. Prettt cool. Will this be released in V4.x, or is it slated for V5?
Same error! Running `pnpm i --fix-lockfile` does not change the lockfile, but in CI I keep getting an error. This is with a project that has a peer dependency listed...
Yeah, I was on v7.30.1. After upgrading to v8, I can confirm that running `--fix-lockfile` fixed the issue. Thanks for your help, @ramnes.
I guess the takeaway from this issue is to always use specific versions of external dependencies in CI.
This thread reminds of xkcd 2347: 
Ok so how can resolutions be enforced in Yarn v3? It's not clear from this conversation. Or can they not be enforced at all?
I've changed my mind about this feature. Because this is a template, the README file will end up in all users' instantiated repo. I would prefer not to clutter those...
Because this is a template, the README file will end up in all users' instantiated repo. I would prefer not to clutter those repos with the names of the template...