You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yeah, I know. :P I've yet to merge it to master and announce it as I'm trying to fix Travis CI to test on Node >= v5 to <= 6.4. For some reason NPM itself started to fail on those versions.
Cool, just wanted to provide some extra validation :)
That npm thing sucks. Everyone seems to be really eager to stop maintaining old node versions. I've found that the easiest thing is to just go with the flow and do a new major release here and there that cuts down support to the active LTS versions.
That npm thing sucks. Everyone seems to be really eager to stop maintaining old node versions. I've found that the easiest thing is to just go with the flow and do a new major release here and there that cuts down support to the active LTS versions.
Haa, only dead fish go with the flow. :P I'm sticking in there with support for old versions, as I think people have, or should have, better things to do than constantly upgrade their environments for possibly little gain. I personally use ancient Node.js versions for as long as I can. Fortunately few security issues affect my run of the mill usage, so so far I've managed to save quite a lot of time. :P
That's really admirable. In a less imperfect world, these testing tools should be the last man standing and only abandon those old versions when nobody else needs to test anything with them. But even mocha is node.js 10+ now.
Here-here! I don't intend to drop support for any Node.js version on any of my own libraries. :)
Ah, I didn't know Mocha's v10+. I'm still using the same old version I used years ago. :P Fortunately the feature set of Mocha, last I checked, is fairly minimal, so it should be simple to implement from scratch. :)
7 commit comments
papandreou commentedon Jun 13, 2020
This does fix the problem we saw in unexpected-mitm mentioned by Alex in #66 (comment) 😌
moll commentedon Jun 13, 2020
Yeah, I know. :P I've yet to merge it to master and announce it as I'm trying to fix Travis CI to test on Node >= v5 to <= 6.4. For some reason NPM itself started to fail on those versions.
papandreou commentedon Jun 13, 2020
Cool, just wanted to provide some extra validation :)
That npm thing sucks. Everyone seems to be really eager to stop maintaining old node versions. I've found that the easiest thing is to just go with the flow and do a new major release here and there that cuts down support to the active LTS versions.
moll commentedon Jun 13, 2020
Of course, thanks for your keen eye! ;)
Haa, only dead fish go with the flow. :P I'm sticking in there with support for old versions, as I think people have, or should have, better things to do than constantly upgrade their environments for possibly little gain. I personally use ancient Node.js versions for as long as I can. Fortunately few security issues affect my run of the mill usage, so so far I've managed to save quite a lot of time. :P
papandreou commentedon Jun 13, 2020
That's really admirable. In a less imperfect world, these testing tools should be the last man standing and only abandon those old versions when nobody else needs to test anything with them. But even mocha is node.js 10+ now.
moll commentedon Jun 13, 2020
Here-here! I don't intend to drop support for any Node.js version on any of my own libraries. :)
Ah, I didn't know Mocha's v10+. I'm still using the same old version I used years ago. :P Fortunately the feature set of Mocha, last I checked, is fairly minimal, so it should be simple to implement from scratch. :)
papandreou commentedon Jun 14, 2020
Or just keep using that old version. (I’ve been trying hard and so far resisted the temptation to write a test runner, haha)