I am rewriting parts of pnpm using reactive programming. It looks a lot better and I think it will help to write more complex/performant algorithms.
However, I am just learning reactive programming, so I'd appreciate if someone more experienced could do code reviews
has anyone experience with reactive programming?
package.json, and more powerful lifecycle scripts keep cropping up for example. I am working on a bunch of ideas to solve these frequent annoyances for myself in the form of more npm modules (and others have attempted with modules like nps and npm-run-all), but ultimately there would be a lot less need for hacky/workarounds if such features were supported in [p]npm core. So I'm just wondering whether your opinion is generally "pnpm is solely focussed on speed/disk space efficiency over regular npm", or more "open to other improvements over npm, which can help pnpm gain more traction"… what are your thoughts?
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-clientwhich 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-registryanymore?
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
