-
Notifications
You must be signed in to change notification settings - Fork 12k
@angular/cli upgrade breaks karma/jasmine sourcemap reporting #14457
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Milestone
Comments
fwiw, I also added this to one of my spec files to help catch the problem during my test suite rather than manually noticing it has broken:
|
mgechev
pushed a commit
that referenced
this issue
May 21, 2019
…rma webpack plugin `sourceMap` option can be either a boolean or an object,we need to normalize it before trying to get the `script` value. Fixes #14457
mgechev
pushed a commit
that referenced
this issue
May 21, 2019
…rma webpack plugin `sourceMap` option can be either a boolean or an object,we need to normalize it before trying to get the `script` value. Fixes #14457
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
🐞 Bug report
Command (mark with an
x
)Is this a regression?
Yes. Sourcemaps in karma/jasmine worked fine up to and including@angular/cli 8.0.0.beta.9, but from beta.10 to current (rc.4 today) sourcemaps no longer work.
Description
Example working output from beta.9:
Example broken output from beta.10+:
🔬 Minimal Reproduction
ng test
and ensure test passes.ng test
again and note you get a line number such asat UserContext.<anonymous> (src/app/app.component.spec.ts:32:18)
ng update --next --all --force
to update to something more recent than 8.0.0.beta.10ng test
and note line numbers no longer help you find your spec in app.component.ts. Instead you see something like this:🔥 Exception or Error
n/a
🌍 Your Environment
ng version:
Anything else relevant?
Not that I know of.
The text was updated successfully, but these errors were encountered: