It would really help if the released distribution of jshint would be available out of the box.
Sample use-case: webjar (http://www.webjars.org/) creation which includes the distribution directly from the source.
I don't get it. Are you suggesting adding versioned bundles to the repo?
I'm not sure what this is asking for, either. If it is to make a folder in the source tree for each release (like with the folder named the version number) that won't make sense, as that's that git tags already do.
What I ask for is to create dist folder holding built jshint resources based on sources from current branch. So, there is no need to keep all versions, but only one. Does this make sense?
Sorry, we're not going to do this.
Could you at least provide the reason? Thanks.
We will provide separate download links for "release" versions of JSHint when 1.0.0 is shipped. As for the repo, I don't think running npm install && node make.js build is bad enough to look for other solutions.
npm install && node make.js build