Upgrade Yarn to v3
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- github-actions, javascript
- Domain
- build-system, ci-cd
Research direction
Use the module template as the reference, then update .yarnrc, .yarnrc.yml, .yarn/releases, .yarn/plugins, package.json, scripts/prepack.sh, and the build-lint-test GitHub workflow. Run the tests before building a local package, then run yarn pack to verify the prepack script and confirm the Yarn v3 configuration works.
Written by the indexing model from the issue text.
Description
This project is using Yarn v1 for managing dependencies and running package scripts. However, we're using Yarn v3 in all of our projects. We should do the same here.
Please use the module template as a guide for completing this ticket.
- Remove
.yarnrc(this is replaced with.yarnrc.ymlin Yarn v3) - Copy over
.yarnrc.yml,.yarn/releases,.yarn/plugins - Add a
packageManagerfield topackage.jsonand use the same value as in the module template - Copy
scripts/prepack.shover - Rename the
prepublishOnlypackage script inpackage.jsontoprepack - Update the
build-lint-testGitHub workflow to runyarn --immutableinstead ofyarn --frozen-lockfile
You can test that the prepack script works by running yarn pack. In this case the tests should be run before a local version of the package is built.
- Dominant language
- JavaScript
- Stars
- 43
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MetaMask/etherscan-link
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
MetaMask/etherscan-link#88 ·
All issues in MetaMask/etherscan-link
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
FuRongJun-1999/dsh-memory#56 ·
Maintainers usually reply within 1 day
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pgadmin-org/pgadmin4#10503 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
521xueweihan/HelloGitHub#3856 ·
-
needs-ac
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Ikalus1988/MisakaNet#2845 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
rage/ohjelmointi-26#23 ·