saas-express-starter-kit VS feathers

So I have been working on a SaaS starter kit - a boilerplate code for a SaaS app, using node and express. Now that it has become useful to some people and the code is growing, I want to make sure thag the developer experience is not lost in an attempt to add more features. I thought having a clear project goals with principles(e.g. no opinion about styling) to follow will help with this. So here I have written down the goals and the principles that will make DevX better, need your feedback what other principles should I add? TIA

Best comment on how to structure your web app. There's a GitHub repo with boilerplate to follow this pattern

Agree. And that's where express boilerplate such as saas-express-starter-kit can become handy.

How will we do it within a week? We will use this starter kit template to start with common things structured and built out of the box (e.g. auth, email, events, etc.)

I choose Express, always. To speed up further, use the boilerplate - https://github.com/makeitcount/saas-express-starter-kit

It won't be a small discussion. Let's discuss this on the GitHub repo issues

For backend this might help https://feathersjs.com. I’m not affiliated with them, just a happy user.

Community stats: Feathers.js has a small but active community with 14.8k stars and 761 forks on GitHub.

The project has gained almost 15k GitHub stars and 26k npm weekly downloads. The Feathers library is widely known for its simplicity and ease of integration with various databases, and it also comes with excellent documentation to help you get started.

Feathers.js - fully fledged backend framework, with almost anything out of the box

Feathers.js

For anything CRUD or that can be modeled as such, I use FeathersJS (https://feathersjs.com/).

Feathers – Realtime Node Microservice Framework

Is there something like Feathers | The API and Real-time Application Framework (feathersjs.com) ?