I would just like to disagree on the &quot;high quality&quot; of modules. Personally I worked for a year in a very long lasting project about a specific type of social network. In the team I was the first one to push for the use of nodejs, react and mongo and... my god if I regretted it.<p>The quality of node package is very bad in general. Like the most part are totally garbage. I don&#x27;t know from where you come and what you used before, I worked only with java, php and ruby for the backend and in those i found:<p>- far higher Documentation quality... like, node modules documentation is not even REMOTELY comparable: it is often extremely outdated, with very poor examples, the most of the times these example are not even working or are using functions deprecated since 3-4 versions of the module itself.<p>- a infinite amount of bugs and undocumented behaviors rarely already reported and, when reported, just ignored for months. I usually would find infinite workarounds instead of solutions<p>- extreme use of &quot;I can do it better, so here my fork&quot;. I passed the big part of the time running from bug report to bug report and reading in the comments discussions about &quot;The main maintainer of this package does not want to solve this problem of mine... so i made this other module, totally identical to this one but I just added this little hack, which totally broke the standard way of doinf things of this module, some functionalities I needed and never implemented the last 8-9 months of commits here.&quot; and chain this. Like this happened a dozen time each months when someone suggested &quot;Why we don&#x27;t try this module that says it solve our needs?&quot;<p>- No standards anywhere.