On 4/19/14 10:30 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> Thanks for trying it. Gjslint is the Google Closure Linter that should >>be >> mentioned in the READme. > > >Thanks it is mentioned in the README and isn't too hard to install but >wont install as described due to permission issues on OSX. I'm not clear what you had to do to get gjslint to run. Can you describe here or add to the README? > >The JShint README instructions could do with a little more than the URL >as there's a few dozen version there. >http://www.jshint.com/install/ > >Tried installing the node.js one (via npm install jshint) but still got >an error running ant. > >Turns out you need to do this - which is mentioned on the JShint >documentation page not the download page. >npm install jshint -g > >And again you'll have permission issues (os OSX) that you will need to >get around. Was there permission issues beyond using -g? I honestly don't recall hitting these, but it's been several months since. > >The amount of pre-requisites there is certainly a barrier for people to >try this out. I think, like the Flex SDK, most folks will use the binary packages and won't be blocked by these issues. Maybe for a future release we'll take out the linting from the builds for the source package but keep them for the repo builds. So did it finally build for you? Thanks, -Alex
