You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't a bug. The pnpm linker relies on the filesystem (same as the node_modules one), so its case sensitivity behaviour depends on the filesystem sensitivity. The OSX filesystem is case insensitive, so packages with files relying on insensitivity cannot work.
PnP doesn't have this problem since the content of the zip archives is managed by Yarn itself.
I don't think Yarn can do anything to actually let me use both a.js and A.js, but it could a) detect the issue, b) offer to use pnp, and c) offer to say "I know what I'm doing, please just overwrite one of the files". Yarn 3.7.0 seems to overwrite the files and so does pnpm.
I mean, of course there's a strong argument that the package should simply be fixed and it's not Yarn 4's problem.
But I feel like it's somewhat dampened by the fact that all (?) package managers pre Yarn 4, including Yarn 3 with any nodeLinker, will install this package. So it might be a long battle.
Self-service
Describe the bug
See react-icons/react-icons#888.
A package containing both
GiHeadshot.esm.js
andGiHeadShot.esm.js
breaks Yarn at the linking phase:Everything is ok with the
pnp
linker. Everything was also ok at yarn 3.7.0.To reproduce
Sherlock not provided because the Sherlock links doesn't work.
Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: