Add package.json

[marrs]

I needed to add this in order to be able to include PhantomCSS as a dependency of a project of mine. I'm sure you'll want to correct some of the info in the package.json, which is simply created with npm init.

[marrs]

Oh, just realised that this isn't a node app. My bad. In that case, would you recommend another way to require this as a library for an external project?

[jamescryer]

There is a lot to be said about the copy/paste approach to library version management ;)

Otherwise, maybe add your PhantomCSS fork as a Git sub module to your project (assuming it's in Git)?

[marrs]

Yeah, but I wanna play with the cool kids. :)

Actually, answering my own question, package.json is a CommonJS spec, so I think it could still be useful to include it. Narwhal looks like it could be a good alternative to npm for managing this

[jamescryer]

I don't think this is worth adding at the moment, that's not to say that users can't create there own package.json files.

I do want PhantomCSS to become installable via NPM, now that PhantomJS has better native support for modules this makes sense. Will probably look to do that after working on SlimerJS support, another instigator for proper versioning. Thanks.