Thats one of my primary issue with the Node community.
When I wrote Go for a few months I was blown away by how many projects I came across that hadn't had a commit to their repo in 3-4 years but people were still recommending them, the author just marked their project as 'feature complete' and all they planned on doing was bugfixes. It was a breath of fresh air.
Churn is built so deeply into the JS ecosystem that things breaking on the way is inevitable.
It's partially my fault for liking to be on recent versions of things, but even on a LTS release of node they released a [build where utf+8 strings were broken](https://github.com/nodejs/node/issues/54543) and our builds were failing silently.
Comments
Thats one of my primary issue with the Node community.
When I wrote Go for a few months I was blown away by how many projects I came across that hadn't had a commit to their repo in 3-4 years but people were still recommending them, the author just marked their project as 'feature complete' and all they planned on doing was bugfixes. It was a breath of fresh air.
Churn is built so deeply into the JS ecosystem that things breaking on the way is inevitable.
It's partially my fault for liking to be on recent versions of things, but even on a LTS release of node they released a [build where utf+8 strings were broken](https://github.com/nodejs/node/issues/54543) and our builds were failing silently.