lightproxy VS hammer

NX repositories build slower, drop 1000's of dependencies in your project and has configurations so verbose you need vscode plugins to drive it (also I didn't like that I had to drop in project scaffolding templates to provision new library or application types). I disliked using it so much I went ahead and built this thing https://github.com/sinclairzx81/hammer.

My development workflow is principally based on https://github.com/sinclairzx81/hammer which is esbuild tooling I wrote myself. I think these days, if you're using TS and want the rapid development workflow, anything that is leveraging esbuild or swc under the hood will be a good thing to pick. So Vite ticks the esbuild box.

I use https://github.com/sinclairzx81/hammer. It provides watch / reload workflows for both node and browser development and it scales from single applications into large mono repository projects. It takes one dependency (esbuild) and needs next to no configuration to use.

I gave up on community build tooling and ended up rolling my own tools. https://github.com/sinclairzx81/hammer. It's difficult to find any tooling in the community that does all the things you may need it to. I found by investing the time into developing tools to align to my workflows, I'm free to modify those tools without getting bogged down in ecosystem plugins, or arcane configurations, or whatever else.

If you just want to get going, you can try https://github.com/sinclairzx81/hammer, (disclaimer I wrote this), or https://parceljs.org/ . Both are zero configuration and will allow you to add in frameworks as you need them (rather than relying on the kitchen sink project bootstrappers like create-react-app).