Dioxus: Difference between revisions

(2 intermediate revisions by 2 users not shown)

Line 1:

[https://dioxuslabs.com Dioxus] is a full-stack Rust app framework for web, desktop, mobile, and more.

[https://dioxuslabs.com Dioxus] is a full-stack [[Rust]] app framework for web, desktop, mobile, and more.

=== Troubleshooting ===

Line 10:

rust Wasm file schema version: 0.2.99

this binary schema version: 0.2.97

</syntaxhighlight>There are two solutions to solving this:

</syntaxhighlight>

===== Why does this happen? =====

Unlike most Rust crates, ''wasm-bindgen'' doesn't follow [https://semver.org semantic versioning (SemVer)]. This means even a patch version difference (like 0.2.97 vs 0.2.98) can contain breaking changes or incompatibilities.

When you install ''dioxus-cli'' from Nixpkgs, it uses the exact versions of dependencies specified in the packages lock file, just like running <code>cargo install dioxus-cli --locked</code>. The versions present in the packages lock file are chosen '''at publishing time'''.

When you add ''dioxus'' as a dependency in your project's ''Cargo.toml'' (or any other crate that requires on ''wasm-bindgen''), [https://doc.rust-lang.org/cargo/reference/resolver.html#semver-compatibility Cargo assumes that all dependencies follow SemVer], and pulls in the latest SemVer compatible version of ''wasm-bindgen.'' This will likely be a different version than was present in the ''dioxus-cli'' lock file, since ''wasm-bindgen'' tends to release quite often.

There are two solutions to solving this:

# ~~Downgrade~~ ''wasm-bindgen'' to the version that ''dioxus-cli'' expects.

# Pin ''wasm-bindgen'' to the version that ''dioxus-cli'' expects.

# Update ''dioxus-cli'' to use a newer lock file.

===== ~~Downgrading~~ ''wasm-bindgen'' =====

===== Pin ''wasm-bindgen'' =====

Within your ''Cargo.toml'' file, force ''wasm-bindgen'' to use the expected version.<syntaxhighlight lang="toml">

Within your ''Cargo.toml'' file, force ''wasm-bindgen'' to use the expected version by pinning it.<syntaxhighlight lang="toml">

[dependencies]

wasm-bindgen = "=0.2.97"

Line 31:

Line 40:

e.g. https://crates.io/api/v1/crates/dioxus-cli/0.6.0/download

Extract the file, ''cd'' into the directory, and run ''cargo update''. You should be able to see the ''wasm-bindgen'' version being updated.<syntaxhighlight>

Extract the file, <code>cd</code> into the directory, and run <code>cargo update</code>. You should be able to see the ''wasm-bindgen'' version being updated.<syntaxhighlight>

Updating wasm-bindgen v0.2.97 -> v0.2.99

</syntaxhighlight>Copy the newly updated lock file into your project (here called ''Dioxus.lock''), and override the Nixpkgs version.<syntaxhighlight lang="nix">

Line 46:

Line 55:

</syntaxhighlight>

==== ''~~Choosing~~ wasm-bindgen-cli ~~version~~'' ====

==== Choosing ''wasm-bindgen-cli'' version ====

You will also want to ensure the version of ''wasm-bindgen-cli'' matches whatever is in your lock file.<syntaxhighlight lang="nix">

cargoLock = builtins.fromTOML (builtins.readFile ./Cargo.lock);

@@ Line 1: / Line 1: @@
-[https://dioxuslabs.com Dioxus] is a full-stack Rust app framework for web, desktop, mobile, and more.
+[https://dioxuslabs.com Dioxus] is a full-stack [[Rust]] app framework for web, desktop, mobile, and more.
 === Troubleshooting ===
@@ Line 10: / Line 10: @@
    rust Wasm file schema version: 0.2.99
       this binary schema version: 0.2.97
-</syntaxhighlight>There are two solutions to solving this:
+</syntaxhighlight>
+===== Why does this happen? =====
+Unlike most Rust crates, ''wasm-bindgen'' doesn't follow [https://semver.org semantic versioning (SemVer)]. This means even a patch version difference (like 0.2.97 vs 0.2.98) can contain breaking changes or incompatibilities.
+When you install ''dioxus-cli'' from Nixpkgs, it uses the exact versions of dependencies specified in the packages lock file, just like running <code>cargo install dioxus-cli --locked</code>. The versions present in the packages lock file are chosen '''at publishing time'''.
+When you add ''dioxus'' as a dependency in your project's ''Cargo.toml'' (or any other crate that requires on ''wasm-bindgen''), [https://doc.rust-lang.org/cargo/reference/resolver.html#semver-compatibility Cargo assumes that all dependencies follow SemVer], and pulls in the latest SemVer compatible version of ''wasm-bindgen.'' This will likely be a different version than was present in the ''dioxus-cli'' lock file, since ''wasm-bindgen'' tends to release quite often.
+There are two solutions to solving this:
-# Downgrade ''wasm-bindgen'' to the version that ''dioxus-cli'' expects.
+# Pin ''wasm-bindgen'' to the version that ''dioxus-cli'' expects.
 # Update ''dioxus-cli'' to use a newer lock file.
-===== Downgrading ''wasm-bindgen'' =====
+===== Pin ''wasm-bindgen'' =====
-Within your ''Cargo.toml'' file, force ''wasm-bindgen'' to use the expected version.<syntaxhighlight lang="toml">
+Within your ''Cargo.toml'' file, force ''wasm-bindgen'' to use the expected version by pinning it.<syntaxhighlight lang="toml">
 [dependencies]
 wasm-bindgen = "=0.2.97"
@@ Line 31: / Line 40: @@
 e.g. https://crates.io/api/v1/crates/dioxus-cli/0.6.0/download
-Extract the file, ''cd'' into the directory, and run ''cargo update''. You should be able to see the ''wasm-bindgen'' version being updated.<syntaxhighlight>
+Extract the file, <code>cd</code> into the directory, and run <code>cargo update</code>. You should be able to see the ''wasm-bindgen'' version being updated.<syntaxhighlight>
 Updating wasm-bindgen v0.2.97 -> v0.2.99
 </syntaxhighlight>Copy the newly updated lock file into your project (here called ''Dioxus.lock''), and override the Nixpkgs version.<syntaxhighlight lang="nix">
@@ Line 46: / Line 55: @@
 </syntaxhighlight>
-==== ''Choosing wasm-bindgen-cli version'' ====
+==== Choosing ''wasm-bindgen-cli'' version ====
 You will also want to ensure the version of ''wasm-bindgen-cli'' matches whatever is in your lock file.<syntaxhighlight lang="nix">
 cargoLock = builtins.fromTOML (builtins.readFile ./Cargo.lock);