node-typescript-architecture VS rivets

It's opinionated, and it's self promotion, but this is what I've used for every project of mine since 2020: https://github.com/jbreckmckye/node-typescript-architecture

Self-plug: I wrote this Node / TypeScript port of "clean architecture" to typed, functional JavaScript two years ago - and it's served me well on every production project ever since

https://github.com/jbreckmckye/node-typescript-architecture

Node TypeScript Architecture repo by Jimmy Breck-McKye (https://github.com/jbreckmckye/node-typescript-architecture) as a fan of TypeScript this will be extremely helpful for me to see how to structure a TS based Node app

I would also say that certain practices are invaluable for working efficiently, just as they are in a job. I don't unit test my open source work particularly religiously - to be honest, I don't feel it gives me much more confidence. But I do have a personal architecture (based on ports and adapters, if you're interested), that I stick to because it always allows me to keep my pure logic and IO / effects code strictly separated.

May I share this? https://github.com/jbreckmckye/node-typescript-architecture

I use http://rivetsjs.com/ in a production intranet project. At the time I started using it I wanted a lightweight alternative to angular/vuejs. I didn’t want the junior devs at the customer to have to learn webpack, etc, but I did want two way data binding, and wanted as lightweight as possible. It has met those needs, and more - it supports creating web components so has let me do reusable code bits also. My main gripe is it’s somewhat stagnant, and there isn’t the ecosystem of components and help like vue or angular.

Still, I’d recommend it for small projects where you need binding.