[Discussion] Yarn & binaries
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.1k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
You mention that Yarn berry is designed to be able to support packages for PHP, Python, Ruby, etc. I was wondering if it's also designed for binaries.
Imagine
{
"name": "my-app",
"dependencies": {
"react": "npm:react@16.8.6",
"parcel": "github:parcel-bundler/parcel@1.12.3",
"node": "nix:nodejs@12.2.0",
"psql": "nix:postgresql@11.3.0"
}
}
Meaning that yarn install is all I have to do to setup a project, rm -rf path/to/project/repo to remove the project and all it's dependencies, and, with zero-install, yarn stop && git pull && yarn start to deploy to production.
How awesome would that be..
Contributor guide
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.
Research direction
The issue names no files, tests, or implementation entry points. Start by determining whether Yarn Berry has an existing design for installing and removing non-JavaScript binaries, then define the supported package sources, lifecycle behavior, and acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100