Kristoffer K.

Pretty sure this is a duplicate of https://github.com/yarnpkg/berry/issues/1039

Bisected to b47fc327fca13c7ea48f23974ed44a31d7d1eb18 / https://github.com/yarnpkg/berry/pull/3631 @paul-soporan

> I cannot seem to check if the github action passed or not, I can't see it running :( I updated the path in https://github.com/yarnpkg/berry/pull/4482/commits/747caad0532df420241187f57cd1fe1b49dd8bad, it's running now.

This is working as expected, the `child` workspace doesn't declare `axios` as a (dev)dependency. Peer dependencies need to be provided by the parent and in this case there isn't one.

We haven't added support for pnpm yet

It seems like your CI is using a different version of Yarn than what you're using locally, are you running `yarn set version ...` on your CI?

> RUN yarn set version berry That will resolve to the latest version which at the time of writing is v3.2.4. > Should that be 'stable' instead? `stable` and `berry`...

That should do it, I do something similar in my Dockerfile's combined with the following `.dockerignore` ```dockerignore .yarn/* !.yarn/cache !.yarn/releases !.yarn/plugins !.yarn/patches .pnp.* ```

The documentation you're referencing is for modern versions of Yarn, classic versions of Yarn wont necessarily support the same patterns that modern does. @arcanis updated classic in https://github.com/yarnpkg/yarn/commit/63cf0ac1190b3490ce2a64fd07e6210fe4bf234b to support...

Make sure the `pnpUnpluggedFolder` isn't in the same folder as `cacheFolder`. You can try the following: ```yaml cacheFolder: ./dependencies/cache pnpUnpluggedFolder: ./dependencies/unplugged ```