Kristiyan Kostadinov b76be83b4d fix(core): animation sometimes renderer not being destroyed during HMR (#59574) ... These changes aim to resolve the issue that prompted #59514. The animations module is a bit tricky for HMR, because it schedules the destruction of its renderer after the currently-running animations are done. If there are no running animations, the renderer gets destroyed next time around. This is a problem, because it means that the styles can stay around for a long time. These changes resolve the issue by: 1. Moving the cleanup of the renderer to after the destruction of the old view. This ensures that the usual clean up flow has been kicked off. 2. Flushing the animations when a component is replaced to ensure that the renderer is cleaned up in a timely manner. PR Close #59574		2025-01-16 11:36:43 -08:00
..
browser	fix(core): animation sometimes renderer not being destroyed during HMR (#59574)	2025-01-16 11:36:43 -08:00
src	docs(animations): update position parameter to be a decimal (#57927)	2024-12-17 09:28:02 -08:00
test	refactor(core): Migrate all packages with the explicit-standalone-flag schematic. (#58160)	2024-10-14 14:58:57 +00:00
BUILD.bazel	refactor(platform-server): Add an ssr benchmark setup. (#57647)	2024-10-04 10:45:22 -07:00
index.ts	refactor: update license text to point to angular.dev (#57901)	2024-09-24 15:33:00 +02:00
package.json	build: update Node.js to match Angular CLI engines (#56187)	2024-06-03 18:00:46 +00:00
PACKAGE.md	docs: Use new Urls to drop the docs url mapper (#55043)	2024-04-09 12:23:09 -07:00
public_api.ts	refactor: update license text to point to angular.dev (#57901)	2024-09-24 15:33:00 +02:00