4 ms·

Took an interesting twist at the end and it turned out to be an npm build tooling problem om windows so republishing it without figuring that out wouldn't have

Took an interesting twist at the end and it turned out to be an npm build tooling problem om windows so republishing it without figuring that out wouldn't have fixed it. Perfect demonstration of why you don't want to behave so dramatically like eric-tucker did. One bit of new information hits that changes the foundation of your stance and you look like a complete asshole.

BinaryIdiot 9y ago
To be fair republishing would have been really quick and saw the issue occur again which may have helped diagnose the issue. Unfortunately no one ever states how it was published or what versions / systems were used. node has had multiple different issues with running and doing things properly on Windows over the various releases; if it was stated earlier that Windows was used to publish I think people would have immediately started looking at that (I know I would have; anytime a friend of mine has an issue with node or npm that's the first thing I ask). I know macOS is a popular system to do node development on but the node folks, at least seem to, forget Windows exists. Also to be fair, a lot of them looked like complete assholes
joatmon-snoo 9y ago
The problem that eric-tucker raised, a very valid one, is that the corruption of file metadata in the published release posed a serious stability risk for anyone whose environment depends on uglify-js. At the very least, from the comments still present (i.e. not deleted) on the issue, it seems absurd to me that the maintainers closed the issue without either (1) publishing a workaround or (2) resolving the issue in production. Similarly, though, I find it reprehensible that it took so long for someone to step forward and help trace the issue - or even make an offer to do so. On a broader note: by now, I think it is a true and established fact that there is no such thing as bug-free software. Bugs exist everywhere, and there is plenty of code out there to defend against the existence of such bugs. It is absolutely and undeniably negligent to say that you won't fix a demonstrable issue in a software release because it triggers known issues in other software, especially when a non-harmful remedy is at hand.

BinaryIdiot 9y ago

To be fair republishing would have been really quick and saw the issue occur again which may have helped diagnose the issue. Unfortunately no one ever states how it was published or what versions / systems were used. node has had multiple different issues with running and doing things properly on Windows over the various releases; if it was stated earlier that Windows was used to publish I think people would have immediately started looking at that (I know I would have; anytime a friend of mine has an issue with node or npm that's the first thing I ask). I know macOS is a popular system to do node development on but the node folks, at least seem to, forget Windows exists. Also to be fair, a lot of them looked like complete assholes

joatmon-snoo 9y ago

The problem that eric-tucker raised, a very valid one, is that the corruption of file metadata in the published release posed a serious stability risk for anyone whose environment depends on uglify-js. At the very least, from the comments still present (i.e. not deleted) on the issue, it seems absurd to me that the maintainers closed the issue without either (1) publishing a workaround or (2) resolving the issue in production. Similarly, though, I find it reprehensible that it took so long for someone to step forward and help trace the issue - or even make an offer to do so. On a broader note: by now, I think it is a true and established fact that there is no such thing as bug-free software. Bugs exist everywhere, and there is plenty of code out there to defend against the existence of such bugs. It is absolutely and undeniably negligent to say that you won't fix a demonstrable issue in a software release because it triggers known issues in other software, especially when a non-harmful remedy is at hand.