Skip to content

feat: isolate Angular runtime per render#1

Merged
Lojhan merged 4 commits intomainfrom
feat/isolated-angular-runtime
Apr 20, 2026
Merged

feat: isolate Angular runtime per render#1
Lojhan merged 4 commits intomainfrom
feat/isolated-angular-runtime

Conversation

@Lojhan
Copy link
Copy Markdown
Collaborator

@Lojhan Lojhan commented Apr 7, 2026

Summary

  • replace shared TestBed fixture management with isolated Angular runtime applications for render and renderHook
  • scope cleanup and fireEvent flushing to the current Poku DOM scope, and add Angular 18/19 zoneless compatibility handling
  • expand Angular lifecycle, cleanup, hook, and scope-isolation coverage and add a publish smoke check script

Validation

  • npm test
  • npm run typecheck
  • npm run check:publish

Notes

  • the publish smoke script was added because package.json referenced tools/publish-smoke.mjs but the file was missing
  • workspace-local file dependency links were removed from the Angular package metadata so the standalone repo stays CI-safe

@Lojhan Lojhan merged commit 3dd78be into main Apr 20, 2026
4 checks passed
@Lojhan Lojhan deleted the feat/isolated-angular-runtime branch April 20, 2026 02:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant