codesandbox / codesandbox/codesandbox-client

Unable to build with Yarn 3 when @codesandbox/common is included in a project

Open
#6,607 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
13.6k
Forks
2.4k
Avg merge
6d 19h
Merged PRs (30d)
2

Description

🐛 bug report

Preflight Checklist

  • [ x] I have read the Contributing Guidelines for this project.
  • [x ] I agree to follow the Code of Conduct that this project
    adheres to.
  • [ x] I have searched the issue tracker for an issue that matches the one I want
    to file, without success.

Description of the problem

Unable to build with Yarn 3 included. Yarn 3 does not like (rightfully) the inclusion of a git repo dependency and will fail with the following error:

YN0018: │ humps@https://github.com/CompuIves/humps.git#commit=7ee34e874c808cf60e7119ee71ac71b8bf2189b7: The remote archive doesn't match the expected checksum
To Reproduce

make a project that uses Yarn 3 and has @codesandbox/common as a dependency
There is a workaround: Use YARN_CHECKSUM_BEHAVIOR=update yarn install, but this turns off Yarn's checksum validation mechanism which introduces a large security hole.

How to fix

Publish CompuIves/humps as an npm package

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure with Yarn 3 in a project that depends on @codesandbox/common, and inspect how it references CompuIves/humps. Verify the fix by replacing the git dependency with a published npm package and confirming Yarn's checksum validation succeeds without YARN_CHECKSUM_BEHAVIOR=update.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, javascript
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.