Came here to say the same thing. The question posed in the title wasn't even answered, unless you count "We have to wait and see" as an answer..
Also I've been using 1.4 for a few weeks now and haven't had any problems :)
Everyone involved is trying to avoid this situation at all costs so I'm pretty confident that it won't happen.
io.js seems more like a bleeding edge (but stable) version of node.
This looks great but I can't get it to work. The repo list never seems to load..
I see you support custom jshint configs which is great, it should probably default to '.jshintrc' though, because it's by far the most common.
It's also worth noting that many people have their jshint options inside 'package.json' under the 'jshintConfig' key.
It'd also be cool to support '.jshintignore' files, which are passed in with --exclude-path
And finally, any plans to support JSCS?
More info:https://yannick.cr/posts/enforcing-coding-rules-in-your-team-with-jscs/post
Repo: https://github.com/jscs-dev
This is the first I've seen of Cha, so I'll talk about that rather than cha-load. I must say it looks very nice. I love the chaining style and that you're making use of the JS Task specification.
Although it looks like yet another gulp/grunt competitor (without the runner) I could see this being useful as part of a web app to orchestrate complex, re-usable tasks. Have you any plans or thoughts about using it this way?
I often define 'tasks' in my node apps as a way of providing a simple interface to a complex procedure and to increase re-usability. I define tasks for things like sending emails, fetching data from 3rd party APIs, etc. At the moment I'm using Agenda[1] for this but I've been thinking about this problem for a while and was planning on writing a module for it (possibly with the Task JS spec) but never found the time. Cha looks like it might be capable of this?
To explain what I mean, imagine something like the following to fetch images from twitter tagged #nodejs and store them in mongodb:
cha()
.twitter({
resource: 'search/tweets',
query: '#nodejs'
})
.filter(function(tweet) {
return tweet.media && tweet.media.length
})
.mongodb({
collection: 'nodejs-photos'
});
[1] https://github.com/rschmukler/agenda
This is the first I've seen of Cha, so I'll talk about that rather than cha-load. I must say it looks very nice. I love the chaining style and that you're making use of the JS Task specification. Although it looks like yet another gulp/grunt competitor (without the runner) I could see this being useful as part of a web app to orchestrate complex, re-usable tasks. Have you any plans or thoughts about using it this way? I often define 'tasks' in my node apps as a way of providing a simple interface to a complex procedure and to increase re-usability. I define tasks for things like sending emails, fetching data from 3rd party APIs, etc. At the moment I'm using Agenda[1] for this but I've been thinking about this problem for a while and was planning on writing a module for it (possibly with the Task JS spec) but never found the time. Cha looks like it might be capable of this? To explain what I mean, imagine something like the following to fetch images from twitter tagged #nodejs and store them in mongodb: cha() .twitter({ resource: 'search/tweets', query: '#nodejs' }) .filter(function(tweet) { return tweet.media && tweet.media.length }) .mongodb({ collection: 'nodejs-photos' }); [1] https://github.com/rschmukler/agendaNice, definitely prettier and more usable than the usual CSS: textarea { resize: vertical }