Default to ignoring jspm bundles, overridable with config

[maxwellpeterson-wf]

Problem

If bundles are defined in config.js, systemjs will load the bundle instead of source files contained in the bundle. The default behavior should be to test source files individually, while allowing users to opt-in to testing using the bundle.

Solution

Add useBundles option. If not specified, karma-jspm will override the bundles config with an empty array.

Testing

• Test in a project that has some jspm bundles defined.
• Ensure the bundle is not requested if useBundles option is not specified in Karma config

@trentgrover-wf @evanweible-wf @guybedford-wf

[guybedford-wf]

Looks great to me.

[trentgrover-wf]

+1

[evanweible-wf]

+10

• created a new project that used jspm and karma-jspm
• created a bundle that had it's configuration injected into config.js
• required a file included in the bundle in a spec
• without this change:
  • the bundle was requested by karma-jspm
• with this change
  • by default, the actual file was requested by karma-jspm instead of the bundle
  • with jspm.useBundles: true in karma.conf.js, the bundle was once again requested by karma-jspm

@charliekump-wf ready for merge

[charliekump-wf]

QA Resource Approval: +1

• [x] Testing instruction
• [x] Dev +1's
• [x] Dev/QA +10 with detail of what was tested
• [ ] Unit test created/updated
  • Not necessary for this change.
• [x] All unit tests pass

Merging into master.