The icssc-website repo has both a package-lock.json and yarn.lock file.
This is suboptimal because it can create edge cases where two versions of dependencies are used to develop, test, and deploy the site.
We've been adopting pnpm throughout ICSSC Projects. Switching to pnpm, or removing either package-lock.json and yarn.lock would solve this issue.
The icssc-website repo has both a
package-lock.json
andyarn.lock
file. This is suboptimal because it can create edge cases where two versions of dependencies are used to develop, test, and deploy the site.We've been adopting pnpm throughout ICSSC Projects. Switching to pnpm, or removing either
package-lock.json
andyarn.lock
would solve this issue.