Foundation update

[Glavin001]

Tasks:

• Closes Add Travis-CI configuration #11, setup Travis CI configuration to perform tests
• Updated the dependencies and configuration to be closer to the latest generator-webapp
• Fixed grunt test Failing #14, test issues: https://travis-ci.org/Glavin001/TasteMusic/jobs/19162734
• Closes Main Music Player #6, implemented SoundManager (SoundCloud actually does this implicitly too if not already included)
• Closes SoundCloud support #5, added support for SoundCloud.

---

Click a track from the list to play it!

[sindresorhus]

?

[Glavin001]

JSHint was not liking that statusText was defined but not being used. I wanted to keep it there as an argument in case we would use it later and did not want to require a lookup in docs for what the third argument passed would be.

[Glavin001]

• Install global grunt-cli in Travis CI configuration, resolves build failure.

[Glavin001]

Thank you for going over my commits, @sindresorhus. Is there anything else you notice that should be amended before merging?

[Glavin001]

• Discuss: should Travis CI test include jshint?

[sindresorhus]

Discuss: should Travis CI test include jshint?

Yes

[Glavin001]

Discuss: should Travis CI test include jshint?

Yes

This is what I originally had by using grunt default as npm test. See comment on issue #11 for details.

I can either change back to what I had: npm test => grunt default, or add another Grunt subtask to test for jshint.

[sindresorhus]

@Glavin001 what you had was fine. I was just thrown off by the grunt default usage, which is moot since grunt does the same thing.

[Glavin001]

I was just thrown off by the grunt default usage, which is moot since grunt does the same thing.

I wanted to be explicit that it was the default task (maybe for Grunt first comers reading the source code, etc) since it would make more sense to be grunt test, however it is not in this case.

@Glavin001 what you had was fine.

I'll change to npm test => grunt.

[sindresorhus]

Awesome stuff :)