Developing serenely with Node.js

We made a new application, and we made it with Node.js The app started off small and grew steadily. More features, more developers. But when the first major refactoring took place, despite having one hundred percent coverage, things didn’t quite go as planned… could it have had to do with JS’ lack of typing? Could it have been avoided by using TypeScript? Or, was our code writing and testing to blame? After a bit more refactoring and bug-fixing, we finally got our app off the ground. Even then, users started to raise issues, and when we couldn’t find answers to their problems in the logs, we started to worry… Coming from a Java background, we were surprised by the underdeveloped nature of Node.js’ frameworks and libraries, especially when it came to managing logs and resolving errors. All these (mis)adventures helped us to take a step back and look at JS development with a fresh pair of eyes. Here, we’ll tell all about this (ongoing) odyssey., We made a new application, and we made it with Node.js The app started off small and grew steadily. More features, more developers. But when the first major refactoring took place, despite having 100% coverage, things didn’t quite go as planned… could it have had to do with JS’ lack of typing? Could it have been avoided by using TypeScript? Or, was our code writing and testing to blame? After a bit more refactoring and bug-fixing, we finally got our app off the ground. Even then, users started to raise issues, and when we couldn’t find answers to their problems in the logs, we started to worry… Coming from a Java background, we were surprised by the underdeveloped nature of Node.js’ frameworks and libraries, especially when it came to managing logs and resolving errors. All these (mis)adventures helped us to take a step back and look at JS development with a fresh pair of eyes. Here, we’ll tell all about this (ongoing) odyssey.