zkochan on v8
test: fix (compare)
npm-registry-client
which is then being written to disk using createWriteStreamAtomic
, while at the same time being piped to unpackStream.local
?
it is downloading a tar with
npm-registry-client
which is then being written to disk usingcreateWriteStreamAtomic
, while at the same time being piped tounpackStream.local
?
yes, the tarball is being saved and unpacked at the same time. We keep the tarball in the store as well (in case the unpacked version gets mutated)
also, there is no
~/.pnpm-registry
anymore?
correct, now the tarballs are saved in the store (~/.pnpm-store
), in the folders where the unpacked packages are
maybe we need a
pnpm store remove [package]
maybe, but right now I don't know how it should behave. Like should it leave the package in the node_modules?
pnpm i
says “this package has been modified in the store…redownloading'
rm -rf ~/.pnpm-store/reigstry…/foo/1.0.0
@vjpr amazing investigation about the EINTEGRITY issue!
you can also contact with the npm team via their discord channel. They are very responsive there: https://discordapp.com/channels/317475976369930241/317477684999487489
As of now I cannot promise any supercool new features in the near future. Although I have a few ideas and there are a few really cool issues open in the repo.
My personal goal is to try to fix as many issues as possible, in pnpm as well as in the ecosystem.
And also I want to refactor and divide the codebase till it is so easy that people will start to contribute.