Would you implement binary search? A feature like git-bisect could be usefull to find breaking changes.
Show HN: Test your JavaScript modules simultaneously in 32 different versions of Node.js
21–30 of 69 posts
Re: Show HN: Test your JavaScript modules simultaneously in 32 different versions of Node.js
#22Would you implement binary search? A feature like git-bisect could be usefull to find breaking changes.
Haven't thought about that but it makes a lot of sense to have that. If you don't mind, could you open up a issue on Github, explaining how you can imagine it to work to help you the most? https://github.com/VictorBjelkholm/autochecker/issues/new
Would appreciate that a lot and thanks for the feedback.
Re: Show HN: Test your JavaScript modules simultaneously in 32 different versions of Node.js
#23Why are there 32 different versions of Node.js?
Re: Show HN: Test your JavaScript modules simultaneously in 32 different versions of Node.js
#24Finally... a place to make sure my left pad module works cross-version.
Re: Show HN: Test your JavaScript modules simultaneously in 32 different versions of Node.js
#25Dumb question, from someone who doesn't work with Node.js: Why are there 32 versions of it?
Node.js has that 60's free love nudist colony experiment feel.
Re: Show HN: Test your JavaScript modules simultaneously in 32 different versions of Node.js
#26Dumb question, from someone who doesn't work with Node.js: Why are there 32 versions of it?
There are actually 303 versions of node (including iojs, according to the Node Version Manager):
$ nvm ls-remote | wc -l
303
$ nvm ls-remote | grep -oE 'v\d+\.\d+' | uniq | wc -l
47
$ nvm ls-remote | grep -oE 'v\d+' | uniq | wc -l
6
Re: Show HN: Test your JavaScript modules simultaneously in 32 different versions of Node.js
#27Frankly, I feel like this is an indictment of all software development, everywhere. When you need to do this kind of a thing, you are doing it wrong. I do not mean I am doing it any better, I have the same issues e.g. working on Android, but there are probably some fundamental things we could be doing to avoid all these horrible symptoms. Things like NixOS come to mind, where people are actively researching and exper…
What do you recommend for how we could do it better?
Take a look outside of the node.js micro cosmos.
Re: Show HN: Test your JavaScript modules simultaneously in 32 different versions of Node.js
#28This is why I hate ES6. JavaScript used to be a write once, run anywhere language.
We sacrificed that for syntactic sugar.
Re: Show HN: Test your JavaScript modules simultaneously in 32 different versions of Node.js
#29This is why I hate ES6. JavaScript used to be a write once, run anywhere language. We sacrificed that for syntactic sugar.
Then just write es5. It'll still run everywhere forever.
Re: Show HN: Test your JavaScript modules simultaneously in 32 different versions of Node.js
#30This is why I hate ES6. JavaScript used to be a write once, run anywhere language. We sacrificed that for syntactic sugar.
You could write vanilla JS and your code still could fail in some versions of node because of bugs or breaking changes.
And in browsers, the JS language is the same, but the implementation of the various APIs has varied greatly.
So ES6 is not the problem.