Skip to content

Conversation

nicoburns
Copy link
Contributor

@nicoburns nicoburns commented Jul 5, 2025

Splits dioxus-native into two crates:

  • dioxus-native-dom which contains:
    • The DioxusDocument
    • The MutationsWriter
    • Event types and conversions
  • dioxus-native which contains everything else (application, launch, asset handling, etc).

The idea is that for use cases where you want to embed Dioxus Native into another application (e.g. a Bevy game) you can just use dioxus-native-dom and avoid pulling in Winit, Muda, etc.


P.S. dioxus-native-dom could alternatively be called dioxus-native-core. I wasn't sure if it was better to reuse that name or leave being what it used to be.

@nicoburns nicoburns added the enhancement New feature or request label Jul 5, 2025
@nicoburns nicoburns requested a review from a team as a code owner July 5, 2025 00:04
@nicoburns nicoburns added the native Related to dioxus-native label Jul 5, 2025
@nicoburns nicoburns merged commit a4ebdcb into main Jul 7, 2025
20 checks passed
@nicoburns nicoburns deleted the native-dom branch July 7, 2025 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request native Related to dioxus-native
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants