4 ms·
Too bad half the modules on npm wont work in 5+ And I don't blame people for not fixing breaking changes every third month. Ohh the module has less then 100 col
by z3t4 9y ago
Too bad half the modules on npm wont work in 5+ And I don't blame people for not fixing breaking changes every third month. Ohh the module has less then 100 collaborators !? I better not use it then. Ohh it has not been updated within the last month ? Better not use it. The cool project that required beta version of node, now half a year later it's too old.
The best part of nodej is code reuse. Not code re-write! /rant
- jdlshore 9y agoA bit overblown, don't you think?
- realPubkey 9y agoI use node 5+ since like forever. Next to every npm-module works for me. And if not, a node downgrade does not help.
- agmcleod 9y agoI think that person meant npm 5 perhaps?
- deleted 9y ago[deleted]
- realPubkey 9y agoGood point. Indeed npm breaks a lot of things also for me.
- abritinthebay 9y agoLike...?
- abritinthebay 9y agoWhich still isn't true, so I have no idea what they are talking about.
- z3t4 9y agoThe problem is with the ABI and libuv. It's very hard to debug and fix the problems if you do not know C++ I do a lot of systems programming in NodeJS and are depending on those modules to access platform API's.
- abritinthebay 9y agoThat’s surely a problem with C++ and OS tooling rather than npm tho...?
- z3t4 9y agoThe problem is NodeJS semver major, eg breaking changes. And the nodejs modules stop working. And the high frequency of semver major makes it hard to keep up. If you are lucky the module is maintained at all that is.