ExpressoTS

@pedro_vargas2 @madalina_barbu Thank you! We are genuinely thrilled by the swift adoption and growth of ExpressoTS. It energizes our commitment to shaping ExpressoTS as the definitive server-side app builder for the future. We look forward to continuing to innovate and contribute to the tech community with our work. Exciting times!!!

@hymiside Zero pain! If your frontend application is done using React you can easily consume the endpoints on ExpressoTS either using fetch, or axios with no issues.

@domantaspe Thank you for your support! To respond to your query, our philosophical foundations and problem-solving methodologies in the server-side space are fundamentally distinct. Nestjs was conceived primarily in line with Angular, as an opinionated MVC framework. Conversely, ExpressoTS provides two distinct methodologies. The first is an opinionated approach, where we recommend a specific strategy for developing your server-side application. This is strongly predicated on an anemic design with some SOLID principles, enabling a completely decoupled application with components that are simple to test, maintain, read, and integrate for engineering onboarding. Additionally, ExpressoTS offers a non-opinionated version where you have the freedom to structure your project as you see fit, powered purely by the core libraries. Furthermore, a significant point of difference is that ExpressoTS embodies best practices derived from well-established frameworks like Spring Boot and .NET. We're not just looking to create abstraction layers to simplify a developer's job. Our primary goal is to accelerate development, simplify code review, and facilitate maintenance from a leadership standpoint. We aim to tackle genuine challenges rather than merely creating mechanical solutions. Here are some additional points I'd like to highlight: We have versatile providers. Onboarding a new developer is straightforward. Our project structure is light and simple. We require minimal configuration. We support two different project structures (opinionated and non-opinionated versions). We accommodate both MVC and non-MVC architectures. The opinionated template is built on clean architecture. You'll notice the incorporation of concepts such as entities, use cases, repositories, and providers in the opinionated template. Predominantly, you'll experience the tangibility of your creation, instead of feeling like you're constructing a server-side app atop an ambiguous heap of components. These are some of the distinguishing features, to name a few. Give it a try, embrace the philosophy and help us to build something amazing! :)