You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
About a year ago, I started developing a production-ready template with Node.js, Express.js, TypeScript, etc. using routing-controllers as framework/base library. Although this stack was good, routing-controllers was not being maintained by the community, which made me suspicious as I had discovered several issues.
In this issue typestack/routing-controllers#900 It was questioned if the project was dead and the developers did not give an answer, so I wanted to look for an alternative. I evaluated the possibility of using NestJS, but it seemed to me that this framework was going to add too much rigidity to my template and it was going to be too coupled to the framework. After reviewing other frameworks carefully I came across Ts.ED. I can only say that since I discovered it I fell in love with it.
The migration from routing-controllers to Ts.ED was very easy, on the one hand due to the architecture I had chosen to implement the template (Hexagonal Architecture) and, on the other hand, the ease of use of Ts.ED. During the migration I only encountered a single bug, which I reported and in less than three days it was solved.
The template I created is this one: borjapazr/express-typescript-skeleton. If you find it interesting and want to use it as an example of using Ts.ED, go ahead, I would be more than happy.
My intention is to try to use my template as a base for all the Node.js projects that are made in the area where I work in my company.
It only remains for me to say thank you very much. If at any time you need support with the development I will be happy to help 🚀
The text was updated successfully, but these errors were encountered:
🧪 This is my experience and my contribution!
About a year ago, I started developing a production-ready template with
Node.js
,Express.js
,TypeScript
, etc. using routing-controllers as framework/base library. Although this stack was good,routing-controllers
was not being maintained by the community, which made me suspicious as I had discovered several issues.In this issue typestack/routing-controllers#900 It was questioned if the project was dead and the developers did not give an answer, so I wanted to look for an alternative. I evaluated the possibility of using NestJS, but it seemed to me that this framework was going to add too much rigidity to my template and it was going to be too coupled to the framework. After reviewing other frameworks carefully I came across Ts.ED. I can only say that since I discovered it I fell in love with it.
The migration from
routing-controllers
toTs.ED
was very easy, on the one hand due to the architecture I had chosen to implement the template (Hexagonal Architecture) and, on the other hand, the ease of use ofTs.ED
. During the migration I only encountered a single bug, which I reported and in less than three days it was solved.My intention is to try to use my template as a base for all the
Node.js
projects that are made in the area where I work in my company.It only remains for me to say thank you very much. If at any time you need support with the development I will be happy to help 🚀
The text was updated successfully, but these errors were encountered: