Comments (3)
Ah yes, that's an unfortunate side-effect, I'm not sure what would be the solution here 🤔 I suppose Yarn registry could use the archice format as the npm registry, but that would invalidate all the hashes for existing Corepack users.
from corepack.
In the case of Yarn the tarball just contains the same source file as the website. We could add an fetch variant that pulls this one file from the archive rather than the whole archive 🤔
That should even be simplified since the checksum is computed right after the extraction, or writing the file on the disk:
corepack/sources/corepackUtils.ts
Line 195 in a05aec6
from corepack.
Ah yes, that's an unfortunate side-effect, I'm not sure what would be the solution here 🤔 I suppose Yarn registry could use the archice format as the npm registry, but that would invalidate all the hashes for existing Corepack users.
Agreed but that change is kinda late as many user may already wrote hash of yarn.js
into their package.json.
Therefore I prefer @arcanis 's idea by adding an option (maybe on npmRegistry) to extract only the yarn.js
file, as things got really complicated there and this is the simplest solution with least users affected (only those wrote hashes with COREPACK_NPM_REGISTRY
will be broken). But that would be another yarn-berry-specific code branch in corepack.
from corepack.
Related Issues (20)
- this[kClient].connect is not a function HOT 6
- Corepack runs into an internal error with newest iron node image [Proxy issue] HOT 4
- Offline workflow does not work HOT 1
- Corepack error with yarn on enable HOT 2
- Silent option on corepack HOT 1
- Frequent fetch() errors HOT 8
- Can't use `pnpm` via corepack when `COREPACK_HOME` is read-only. HOT 4
- feat: store `packageManager` property also inside the lock file HOT 5
- `COREPACK_INTEGRITY_KEYS` being ignored when corepack is spawned by other tools HOT 2
- Could we support corepack enable --yes? HOT 4
- `corepack install --global [email protected]` doesn't work HOT 2
- corepack installs pre-release version of pnpm `9.1.0-0` HOT 1
- CI/CD runs fail: Type Error: URL.canParse is not a function HOT 6
- corepack install verbose error HOT 4
- Corepack doesn't work properly inside official node docker images. HOT 3
- prepare and enable command is not documented HOT 2
- Add quite mode when download file HOT 1
- Metadata retrieval errors when using `COREPACK_NPM_REGISTRY` in combination with Sonatype Nexus
- `prepare` script blocks correct usage HOT 2
- I'll double-check, but the help should be printed on `corepack -h|--help`:
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from corepack.