Sourcemaps not included in karma configuration
- Dominant language
- JavaScript
- Stars
- 402
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
**I'm submitting a bug report**
* **Library Version:**
0.32.0
**Please tell us about your environment:**
* **Operating System:**
Windows 10
* **Node Version:**
6.11.3
* **NPM Version:**
3.10.10
* **Browser:**
all
* **Language:**
all
* **Loader/bundler:**
Webpack
**Current behavior:**
Creating a new app using Webpack and Karma does not include sourcemaps while debugging karma tests
* **What is the expected behavior?**
To use sourcemaps while debugging karma tests
It appears there was an attempt to include this feature according to the issue here: https://github.com/aurelia/cli/pull/656.
The related PR updated a karma.conf.js file located here https://github.com/aurelia/cli/blob/master/lib/resources/content/karma.conf.js to use sourcemaps.
But the cli is still creating new apps using the karma configs located here
- https://github.com/aurelia/cli/blob/master/lib/resources/test/webpack/babel/karma.conf.js
- https://github.com/aurelia/cli/blob/master/lib/resources/test/webpack/typescript/karma.conf.js
Contributor guide
Research direction
Compare the generated templates in lib/resources/test/webpack/babel/karma.conf.js and lib/resources/test/webpack/typescript/karma.conf.js with lib/resources/content/karma.conf.js, which the issue identifies as already using sourcemaps. Regenerate a Webpack/Karma app and debug its tests to verify that sourcemaps are included in both configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript, webpack
- Domain
- cli, testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100