More declarative style

[ORESoftware]

Hey there!

I developed this over the last week: https://github.com/ORESoftware/npm-link-up

I just discovered your project now. Cool - I wonder if there are others.

One thing I like about my project, is that the tool will search for the packages by name. All you need is a config file with the list of dependency names, and npmlinkup will search for them on the filesystem. So if you happen to move projects around by chance, it will still work fine.

Also, we probably have slightly different algorithms. I tested mine and it should manage circular dependencies just fine. Still have to write more tests for npmlinkup though.

[wclr]

Hi, you may also be interested in this approach to the problem: https://github.com/whitecolor/yalc

[the1mills]

I checked it out, looks too complicated :/

A picture or something would help understand how it works. I think devs are afraid of going too far down the wrong road.

As far as I can tell, my tool (npm-link-up) is the simplest one and requires the least deviation from the norm, but feel free to prove me wrong.

[wclr]

@the1mills you mean yalc? it is really very simple. I think it has another goals then npm-link-up just related. It is not for monorepo, monorepo actually assumes that project has many nested packages and they are managed together that is lerna for (I'm not sure why one would use linking for this case).

Primarily yalc's goal to get rid of using symlinks when working with shared packages that are in progress ( because symlinks it is the part of the workflow that brings most of the problems, that is why I would never use such tool as pnpm for example) and there are some other issues with npm link workflow too. So yalc actually "simulates" installation of the packages as if they were installed normally from the registry, only published code available, isolated node_modules and dependencies, it removes all the frictions with npm link'ed packages.