Get a better usage pattern set up for yalc/zalc, which avoids yarn.lock differing between dev machines (eg. working, streamlined yalc retreat/restore)

debate-map / app

Monorepo for the client, server, etc. of the Debate Map website.

https://debatemap.app

MIT License

73 stars 16 forks source link

Get a better usage pattern set up for yalc/zalc, which avoids yarn.lock differing between dev machines (eg. working, streamlined yalc retreat/restore) #294

Closed Venryx closed 6 months ago

Venryx commented 6 months ago

Achieved the above for the most part... (a bit more flakiness for the yalc-usage process, but better overall, eg. nicer for other devs to have a stable yalc.lock)