Skip to content

V5 WIP - do not merge - #6657

Draft
johnjenkins wants to merge 327 commits into
mainfrom
v5
Draft

V5 WIP - do not merge#6657
johnjenkins wants to merge 327 commits into
mainfrom
v5

Conversation

@johnjenkins

@johnjenkins johnjenkins commented Mar 29, 2026

Copy link
Copy Markdown
Contributor

Description

This is the main branch for the upcoming V5 release. Choc full of new things and some breaking changes

Things it'll address and close

Fixes #6641
Fixes #6630
Fixes #5306
Fixes #6749
Fixes #6798
Fixes #6636

Closes #6578
Closes #6599
Closes #5307
Closes #6107
Closes #4232
Closes #6638
Closes #6649
Closes #6759

Documentation

Does this introduce a breaking change?

  • Yes
  • No

Testing

Other information

johnjenkins and others added 30 commits July 13, 2026 23:55
* fix: v5 npm wizards

* fix(cli): various wizard fixes and improvements
* feat(compiler): new `docs-agent-skill` output target

* chore:

* chore:
* chore: v5 add componentOnReady test coverage & standalone type

* chore: add runtime retry
* feat(runtime): v5 batched componentShouldUpdate

* chore:

* chore: throw warning
* fix(runtime): non-shadow slot forwarding fixes

* chore: formatting

* chore: update test
… order contract (#6823)

* fix(runtime): load order improvements; guarantee parent / child order contract

* chore: trimming / tidying
…pe references across (#6824)

* feat(unplugin): resolve extend types location

* chore: spelling

* chore: spellcheck
* fix(compiler): track type query references (#6825)

* fix(compiler): track type query references

Collect class and enum names used by TypeQueryNode expressions so generated component declarations preserve imports and type-library entries across aliases and re-exports.

fixes: #2482

* refactor(compiler): share alias resolver

Use the compiler's mock filesystem for the type-query fixture and document the updated export/import branches.

* test(compiler): normalize mock paths

* chore: v5 update the deps

---------

Co-authored-by: Langning Zhang <zln1905391059@163.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment