Node.js Compiler – Compiling your Node.js application into a single executable

Re:Node.js Compiler – Compiling your Node.js application int... by microcolonel on Friday May 05, 2017 @02:09AM (#14271443)

One other one is that it has hilariously poor performance, and bizarre failure cases. For some forms of network failures it'll just say "callback called too many times" and crash.

There are literally no worse major package managers.

A good package manager can be misused and still work reasonably well; a bad one doesn't even work all that well when used correctly.

[ Parent | on HN ]

Re:Node.js Compiler – Compiling your Node.js application int... by int_19h on Friday May 05, 2017 @04:24AM (#14271910)

Or how about this for error reporting:

https://github.com/npm/npm/issues/9633

I especially like the part where it says "This is most likely not a problem with npm itself", even though it clearly is a problem with npm itself (as evidenced by non-deterministic nature of the bug).

[ Parent | on HN ]

Re:Node.js Compiler – Compiling your Node.js application int... by abritinthebay on Friday May 05, 2017 @11:52AM (#14274342)

That message is their generic message because ANY error ended up being reported in github as an issue with NPM.

Again, bad dev practice.

[ Parent | on HN ]