Installing Intern using NPM

[vladikoff]

We've discussed this a bit before with @csnover earlier.
Would adding Intern to NPM make the framework easier and more accessible to the users?

[bitpshr]

I think this is a good idea.

I have an open pull request to make an updated Intern Grunt task part of this repository, so being able to distribute everything as a single package via NPM for world domination of JavaScript testing would be a good thing.

+1 for distributing Intern via NPM regardless of the route we take with Grunt.

[vladikoff]

I saw the Grunt Task PR, really awesome! can't wait to use it :)

[csnover]

Yes, it is definitely planned to have this registered as an npm package. The install instructions will be updated when it is.

[csnover]

There is now a registered npm package, but the documentation is not yet updated.

[phated]

Hooray! Thanks Colin!

[milesj]

Awesome, was going to ask for this. However, when trying to install intern through NPM, I keep receiving this error... which is weird because the repo looks fine.

npm WARN `git config --get remote.origin.url` returned wrong result (git://githu
b.com/csnover/sauce-connect-launcher.git) undefined
npm WARN `git config --get remote.origin.url` returned wrong result (git://githu
b.com/csnover/sauce-connect-launcher.git) undefined
npm ERR! git clone git://github.com/csnover/sauce-connect-launcher.git undefined

npm ERR! git clone git://github.com/csnover/sauce-connect-launcher.git undefined

[csnover]

Do you have Git installed?

[milesj]

Yeah that was my mistake, I fixed it already. I have git installed but cygwin couldn't reference it.

[altano]

So I'm confused. This is an open issue for milestone 1.1 and is still open, but intern appears to be available and installable via npm as version 1.0. But the "Using Intern with Grunt" page says:

Install Intern and load the Grunt task into your Gruntfile using grunt.loadTasks('path/to/intern/grunt'); (Intern 1.0.0) or grunt.loadNpmTasks('intern') (Intern 1.1+).

... but loadNpmTasks() fails with Intern 1.0 currently on npm.

So, what does it mean to support loadNpmTasks() with Intern 1.1 if that's not on npm yet? Was that documentation just jumping the gun on the release?

I'm assuming that if I want to use Intern with Grunt right now, I can't use npm and I should just download via git and call loadTasks() pointing at the intern/grunt. Right?

This stuff all looks pretty cool by the way, so thanks to all of you for working on this.

[csnover]

Documentation is always updated to reflect the current state of development. Version numbers are put in the documentation so you know what’s supported or not. The copy of Intern currently available via npm exists to prevent package name squatting and to perform testing of installations via npm and is not yet an officially supported installation method. Official installation support via npm will first appear in 1.1. If you are using Grunt with Intern 1.0, you need to load the tasks as per the 1.0 instructions (loadTasks).

[altano]

That makes sense. I'm still having trouble but I'll start a new issue to discuss it.

[HelloGrayson]

Mega +1