chore: Release 2025-08-01 13:46:47

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@lynx-js/[email protected]

Minor Changes

• Add support for Lynx UI plugin system with configurable options. (#1363)

  • Introduced lynxUIPlugins option in createLynxPreset, allowing userland opt-in to Lynx UI specific plugins.

  • Implemented uiVariants plugin as the first UI plugin, supporting ui-* variant prefixes (e.g. ui-checked, ui-open) with customizable mappings.

@lynx-js/[email protected]

Patch Changes

• Fix crash caused by not removing event listeners during destroy. (#1379)

• Fix missing "type" in "update-list-info" in hydrate (#1392)

@lynx-js/[email protected]

Patch Changes

• Bump Rsbuild v1.4.12 with Rspack v1.4.11. (#1326)

@lynx-js/[email protected]

Patch Changes

• Updated dependencies [e9edca0, 6f37db2]:
  • @lynx-js/[email protected]
  • @lynx-js/[email protected]
  • @lynx-js/[email protected]
  • @lynx-js/[email protected]
  • @lynx-js/[email protected]
  • @lynx-js/[email protected]

@lynx-js/[email protected]

Patch Changes

• feat: support __ElementFromBinary (#1391)

• Updated dependencies []:

  • @lynx-js/[email protected]

@lynx-js/[email protected]

Patch Changes

• feat: support __ElementFromBinary (#1391)

• fix: crash on chrome<96 (#1361)

  Rust v1.82 enables reference type transformations by default wasm-bindgen/wasm-bindgen#4211 (comment)

  wasm2js: support multiple tables WebAssembly/binaryen#7358

  The rust toolchain enables WASM feature reference types by default.

  However this feature is not supported by chromium lower than version 96

  Therefore we found a workaround for it.

  In this implementation we detect if browser supports reference types first.

  If user's browser supported it, we load the wasm file with reference types on, otherwise we load the wasm file with reference types off.

• Updated dependencies [22ca433, 8645d12, 143e481]:

  • @lynx-js/[email protected]
  • @lynx-js/[email protected]
  • @lynx-js/[email protected]
  • @lynx-js/[email protected]

@lynx-js/[email protected]

Patch Changes

• refactor: bundle web-core-server (#819)

@lynx-js/[email protected]

Patch Changes

• feat: support color style for x-textarea (#1382)

• Updated dependencies []:

  • @lynx-js/[email protected]

@lynx-js/[email protected]

Patch Changes

• feat: support __ElementFromBinary (#1391)

• fix: crash on chrome<96 (#1361)

  Rust v1.82 enables reference type transformations by default wasm-bindgen/wasm-bindgen#4211 (comment)

  wasm2js: support multiple tables WebAssembly/binaryen#7358

  The rust toolchain enables WASM feature reference types by default.

  However this feature is not supported by chromium lower than version 96

  Therefore we found a workaround for it.

  In this implementation we detect if browser supports reference types first.

  If user's browser supported it, we load the wasm file with reference types on, otherwise we load the wasm file with reference types off.

• Updated dependencies [22ca433]:

  • @lynx-js/[email protected]
  • @lynx-js/[email protected]

@lynx-js/[email protected]

Patch Changes

• optimize IO for all-on-ui: make startMainThreadWorker async and defer import (#1385)

• Updated dependencies [22ca433, 143e481]:

  • @lynx-js/[email protected]
  • @lynx-js/[email protected]
  • @lynx-js/[email protected]

@lynx-js/[email protected]

Patch Changes

• Support Rspack v1.4.9. (#1351)

@lynx-js/[email protected]

Patch Changes

• feat: support elementTemplate for web (#1374)

[email protected]

@lynx-js/[email protected]

[email protected]

@lynx-js/[email protected]

@lynx-js/[email protected]

@lynx-js/[email protected]

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.