support for pnpm, i.e. "palc"

[dkebler]

I have systems made of several running node processes on each machine(sbc's) that share much if not all of the same dependencies which is one reason I've opted for pnpm. But during development I've come to love yalc (thx @whitecolor) so I end up scrubbing node_modules and installing with yarn. Then I have to go back to pnpm when ready for production testing direct from a proper repository.

Anyway just wondering what might be involved in making a pnpm flavored yalc (i.e. palc) compatible with pnpm. Since pnpm already works similarly to yalc (a local store shared by links (hard links in pnpm's case) "palc" would not necessarily need to maintain its own store. So this might be as simple as writing into the existing pnpm store. One advantage of "palc" is that one would not need to do a yalc link in each process deployment as pnpm already has done this by default. https://pnpm.js.org/

If it's not adding too much overhead into yalc, yalc could just have a --pnpm flag for this behaviour.

Anyone else watching this project interested in this?

[javier-garcia-meteologica]

Just one caveat, in a monorepo with "workspace:" dependencies they have to be resolved before packaging.

[wclr]

I'm using pnpm for most of my projects, have no problems with the workflow, recently I published the version that supports workspace: resolution. See the changelog and readme.

@dkebler so I didn't get your particular issue regarding pnpm and yalc workflow.

[Angra974]

I'm using pnpm for most of my projects, have no problems with the workflow, recently I published the version that supports workspace: resolution. See the changelog and readme.

@dkebler so I didn't get your particular issue regarding pnpm and yalc workflow.

Hi. In my case, when i load "pnpm install" after "yarn add my_package", pnpm put the package in "node_modules/.ignored" and download my_package from npm servers.