build(devtools): fix ng-devtools source maps #62042
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Inline the sources contents in the `js.map` files. This fixes the source maps for the dev app.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a problem with the dev app bundle where esbuild is unable to properly set the
sourcesContentof thejs.mapfiles forng-devtools. They arenull. That's why, the.tsfiles are registered by Chrome DevTools but their contents cannot be loaded.I am not entirely sure why this happens given that the
sourcespaths array is properly set, but inlining thesourcesContentin the map files solves the issue for now which allows us to perform proper debugging in the browser.