CP-821 Move overrides to after karma has loaded

[JeroenVinke]

fixes https://github.com/Workiva/karma-jspm/issues/77

Config.js is loaded after the overrides causing 404 errors on all files. When you move the override to after karma has loaded, the overrides work and tests run normally again.

[zewa666]

Funny I just found the solution few minutes after your PR, so yep agree that this should fix it. Good work @JeroenVinke :+1:

[EisenbergEffect]

Please merge and release with this fix as soon as you can! We really need this.

[ghost]

+1

[maxwellpeterson-wf]

+1 @jayudey-wf let's merge this and do a 2.0.1-beta.2 release

[ghost]

@maxwellpeterson-wf please do it today and remember to tag for npm!

[ghost]

@maxwellpeterson-wf today as in 2 hours ago :)

[maxwellpeterson-wf]

@robertbaker You have to understand that we have a QA and release process that we are required to go through internally. Our team is also very busy with a number of other things not related to this project, however, our QA does plan to get to this today. If that isn't quick enough for you, I'd recommend installing this specific branch of karma-jspm in your project. You can do so with the following command:

$ npm install "git+ssh://git@github.com:JeroenVinke/karma-jspm.git#master"

[EisenbergEffect]

@maxwellpeterson-wf Thanks for addressing this for us! We really appreciate you guys putting the effort in on this plugin.

[jayudey-wf]

QA Resource Approval: +10

• [x] Testing instruction
• [x] Dev +1's
• [x] Dev/QA +10 with detail of what was tested
  • installed into project consuming karma-jspm, verified that tasks were still working as expected
• [ ] Unit test created/updated
• [x] All unit tests pass

Merging into master.

[maxwellpeterson-wf]

@robertbaker tag has been created and published.