Skip to content

Sourcemaps for tests broken since 1.1.2 #6824

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

Closed
Ristaaf opened this issue Jun 28, 2017 · 2 comments
Closed

Sourcemaps for tests broken since 1.1.2 #6824

Ristaaf opened this issue Jun 28, 2017 · 2 comments

Comments

@Ristaaf
Copy link

Ristaaf commented Jun 28, 2017

Bug Report or Feature Request (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request

Versions.

@angular/cli: 1.1.3
node: 7.9.0
os: win32 x64
@angular/animations: 4.2.4
@angular/common: 4.2.4
@angular/compiler: 4.2.4
@angular/core: 4.2.4
@angular/forms: 4.2.4
@angular/http: 4.2.4
@angular/platform-browser: 4.2.4
@angular/platform-browser-dynamic: 4.2.4
@angular/router: 4.2.4
@angular/cli: 1.1.3
@angular/compiler-cli: 4.2.4
@angular/language-service: 4.2.4

Repro steps.

  • ng new smtest

  • cd smtest

  • edit app.component.spec.ts to add a debugger statement

  • ng test

  • open chrome devtools and reload page

  • the debugger statement is hit but it is in the main.bundle.js file, and no ts sourcefile is to be found anywhere!

Desired functionality.

The app.component.spec.ts file should be available for debugging in chrome devtools sources.

Mention any other details that might be useful.

This works fine in angular cli 1.1.1, the app.component.spec.ts file can there be found in context->webpack://->C://smtest->src->app

This was most probably broken by the commit "@angular/cli: correct sourcemap source paths (cf66e6b)"

@filipesilva
Copy link
Contributor

There's another report of this in #6737 so I will close this one as a duplicate.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants