Skip to content

fix(platform-browser): roll back HMR fix#59557

Closed
crisbeto wants to merge 1 commit intoangular:mainfrom
crisbeto:hmr-regression
Closed

fix(platform-browser): roll back HMR fix#59557
crisbeto wants to merge 1 commit intoangular:mainfrom
crisbeto:hmr-regression

Conversation

@crisbeto
Copy link
Copy Markdown
Member

@crisbeto crisbeto commented Jan 16, 2025

Rolls back the changes from #59514 because they ended up being breaking in 3P. We can revisit the internal fix in a different way.

Fixes #59558.

@crisbeto crisbeto added action: review The PR is still awaiting reviews from at least one requested reviewer target: patch This PR is targeted for the next patch release labels Jan 16, 2025
@angular-robot angular-robot bot added the area: core Issues related to the framework runtime label Jan 16, 2025
@ngbot ngbot bot added this to the Backlog milestone Jan 16, 2025
Rolls back the changes from angular#59514 because they ended up being breaking in 1P. We can revisit the internal fix in a different way.

Fixes angular#59558.
@crisbeto crisbeto changed the title fix(platform-browser): avoid issues if renderer is destroyed twice in a row fix(platform-browser): roll back HMR fix Jan 16, 2025
@pkozlowski-opensource pkozlowski-opensource 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 Jan 16, 2025
@pkozlowski-opensource
Copy link
Copy Markdown
Member

This PR was merged into the repository by commit 2fe54a1.

The changes were merged into the following branches: main, 19.1.x

pkozlowski-opensource pushed a commit that referenced this pull request Jan 16, 2025
Rolls back the changes from #59514 because they ended up being breaking in 1P. We can revisit the internal fix in a different way.

Fixes #59558.

PR Close #59557
@michael-small
Copy link
Copy Markdown
Contributor

Thank you for handling this, and so responsively <3. I personally verified with a fork of my SB repro and it worked as intended. Very excited to proceed with my upgrade to the latest version now with this patch.

PrajaktaB27 pushed a commit to PrajaktaB27/angular that referenced this pull request Feb 7, 2025
Rolls back the changes from angular#59514 because they ended up being breaking in 1P. We can revisit the internal fix in a different way.

Fixes angular#59558.

PR Close angular#59557
@angular-automatic-lock-bot
Copy link
Copy Markdown

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 Feb 16, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: core Issues related to the framework runtime target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

HMR will drop styles applied to a component if an HTML element in a component is changed

3 participants