-
-
Notifications
You must be signed in to change notification settings - Fork 287
fix(vite-plugin-angular): fix component HMR with angular 19.1.2 #1563
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
Conversation
✅ Deploy Preview for analog-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for analog-ng-app ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for analog-app ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for analog-blog ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
"nitropack": "^2.10.0", | ||
"nx": "20.1.2", | ||
"playwright": "^1.30.0", | ||
"playwright": "^1.49.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needed to fix the failing e2e tests which broke due to github recently upgrading github actions to use ubuntu 24. Support for ubuntu 24 was only added in playwright 1.45
Happy to make this a separate PR if needed
@mattlewis92 This line needs adjusting also
|
Thanks! Fixed in |
PR Checklist
In angular
19.1.2
component template urls were changed to be relative via angular/angular#59620. Unfortunately this breaks component template HMR with the vite pluginLuckily the fix is pretty straight forward (copied from angular/angular-cli#29386)
What is the new behavior?
Component template HMR works again
Does this PR introduce a breaking change?
Other information
[optional] What gif best describes this PR or how it makes you feel?