Skip to content

fix(@angular/build): ensure com.chrome.devtools.json is consistently served after initial run#30176

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

Merged
merged 1 commit into from
Apr 25, 2025

Conversation

alan-agius4
Copy link
Collaborator

Previously, com.chrome.devtools.json was generated and served correctly on the first run, but subsequent ng serve runs failed to serve the file unless the Angular cache was cleared. This change addresses the inconsistency.

…y served after initial run Previously, `com.chrome.devtools.json` was generated and served correctly on the first run, but subsequent `ng serve` runs failed to serve the file unless the Angular cache was cleared. This change addresses the inconsistency.
@alan-agius4alan-agius4 added action: review The PR is still awaiting reviews from at least one requested reviewer target: major This PR is targeted for the next major release labels Apr 25, 2025
@alan-agius4alan-agius4 requested a review from clydinApril 25, 2025 06:50
@alan-agius4alan-agius4 added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Apr 25, 2025
@alan-agius4alan-agius4 merged commit 05485ed into angular:mainApr 25, 2025
33 of 34 checks passed
@alan-agius4alan-agius4 deleted the chrome-devtools branch April 25, 2025 08:14
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: mergeThe PR is ready for merge by the caretakerarea: @angular/buildtarget: majorThis PR is targeted for the next major release
2 participants
@alan-agius4@clydin
close