Added npm package.json

It's pretty minimal for now because it's only going to be used for specifying the dependency on the grunt task runner and any grunt plug-ins.
Installed the grunt task runner

npm install grunt --save-dev

...so it goes in the package.json also.
Installed grunt-contrib-jshint as a devDependency and added a Gruntfile.js configured to lint the javascript files with 'grunt jshint'
Add grunt-contrib-watch and configure it to run jshint whenever a javascript file changes
Untabify the javascript
Fixing jsHint issues
Final jsHint fixes
Register a default grunt task

So running 'grunt' on the command line will run jshint immediately and then the watch task to watch for changes
Added a simple jasmine unit test

The album model is a simple enough class to start testing. I suspect adding more tests is going to require some refactoring &/or mocking.
If all build steps are successful then copy the files needed to run the app to the spotify folder

~/Spotify (Mac OS X and Linux)
“My Documents\Spotify” (Windows)

- If a file gets removed from the project, it won't delete it from the spotify folder. Perhaps as a simple solution it should clean the destination folder first.
- I've only tested this on Windows
- On Windows, it assumes the user's documents folder is in the default location (otherwise I think it means reading the registry...also, I'm not sure how Spotify deals with this - it could be that the apps have to be in the default location anyway!)
Clean the spotify folder before copying the new files
Revert "Clean the spotify folder before copying the new files"

This reverts commit 36d0d3f352702de05d771921277cc5ec8c31ab2c.

I had second thoughts about deleting the entire contents of a folder. It could
destroy someone's work if they're are developing within the spotify folder.
Added grunt configurations to allow for working in the spotify folder OR a separate folder

The default task runs jshint and jasmine followed by a watch task that will re-run jshint and jasmine whenever a project js file changes.
The deploy task does the same but includes a copy task after jshint and jasmine. The copy task copies the project files to the spotify folder so it can be run.

Use the former if you clone the repository to the spotify folder and do all your work in there. The latter is useful if you prefer to work in a different folder.
Update README.md
Merge pull request #4 from ianreah/gruntify

Gruntify