Use npm workspaces rather than lerna for monorepo dependency managment

[underbluewaters]

I'm using a very outdated version of lerna and npm has gained a lot of monorepo management features since this project started. Using lerna causes a lot of problems:

• It's slow
• SeaSketch uses an out of date version. Upgrading to the latest lerna requires the use of workspaces, and then it becomes unnecessary.
• Simple features like removing a dependency are missing
• I get transient build errors on CI which are hard to debug.

It is time to ditch lerna for a more modern setup.

[twelch]

You might find it doesn't quite do everything you want, simpler always better if it does. I remember reviewing when it came out a couple years ago

[twelch]

Lerna now using Nx is faster.

Turf is now using a combo of pnpm, lerna, monorepolint to coordinate everything it does for reference.

[underbluewaters]

Do you know if there's any archived discussion of adopting those tools for turf?

My thinking now is to keep things as simple as I can get away with. It would be nice to easily adopt something like Bun in the future.

[twelch]

There's a little bit of discussion here, I would say the idea was not to do a complete rewrite, just upgrade and replace when necessary - Turfjs/turf#2555. Note turf already was using monorepolint, which had a follow-on PR to work with pnpm - Turfjs/turf#2557.

I can't tell you exactly which needs necessitated the addition of each tool. I've been considering what to do with geoprocessing in the new year.