Skip to content

Sourcemap not reloading after source code change #30149

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

Open
1 task
Lavanya0402 opened this issue Apr 22, 2025 · 1 comment
Open
1 task

Sourcemap not reloading after source code change #30149

Lavanya0402 opened this issue Apr 22, 2025 · 1 comment
Labels
needs: repro steps We cannot reproduce the issue with the information given

Comments

@Lavanya0402
Copy link

Command

add

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

Whenever I'm in debug mode, I make changes to the code, save it and try to add a breakpoint to the newly added line, the breakpoint is unbound. The sourcemap cannot detect the newly added line.

Minimal Reproduction

Run the application in debug mode.
Make code changes.
Save and wait for it to detect changes and reload.
Set breakpoint in newly added line.
Breakpoint is unbound or breakpoint is set at random location.

Exception or Error


Your Environment

Angular CLI: 19.1.8
Node: 22.14.0
Package Manager: npm 10.9.2
OS: win32 x64

Angular:
...

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1901.8 (cli-only)
@angular-devkit/core         19.1.8 (cli-only)
@angular-devkit/schematics   19.1.8 (cli-only)
@schematics/angular          19.1.8 (cli-only)

Anything else relevant?

No response

@alan-agius4
Copy link
Collaborator

I'm sorry, but we can't reproduce the problem following the instructions you provided.
Remember that we have a large number of issues to resolve, and have only a limited amount of time to reproduce your issue.
Short, explicit instructions make it much more likely we'll be able to reproduce the problem so we can fix it.

If the problem persists, please open a new issue following our submission guidelines.

A good way to make a minimal repro is to create a new app via ng new repro-app and add the minimum possible code to show the problem. Then you can push this repository to github and link it here.

@alan-agius4 alan-agius4 added the needs: repro steps We cannot reproduce the issue with the information given label Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: repro steps We cannot reproduce the issue with the information given
Projects
None yet
Development

No branches or pull requests

2 participants