Bump the dependencies group with 7 updates

[dependabot]

Bumps the dependencies group with 7 updates:

Package	From	To
clap	4.5.2	4.5.4
anyhow	1.0.80	1.0.81
serde_json	1.0.114	1.0.115
markup5ever	0.11.0	0.12.0
thiserror	1.0.57	1.0.58
dioxus	0.4.3	0.5.1
dioxus-web	0.4.3	0.5.1

Updates clap from 4.5.2 to 4.5.4

Release notes

Sourced from clap's releases.

v4.5.4

[4.5.4] - 2024-03-25

Fixes

• (derive) Allow non-literal #[arg(id)] attributes again

v4.5.3

[4.5.3] - 2024-03-15

Internal

• (derive) Update heck

Changelog

Sourced from clap's changelog.

[4.5.4] - 2024-03-25

Fixes

• (derive) Allow non-literal #[arg(id)] attributes again

[4.5.3] - 2024-03-15

Internal

• (derive) Update heck

Commits

• 5e4facf chore: Release
• 8880b0a docs: Update changelog
• 132b5dd Merge pull request #5425 from epage/lit
• df915fe fix(derive): Re-allow expressions for id's
• 8eab48f refactor(derive): Make it easier to work with 'Name'
• be73195 refactor(derive): Clarify tests
• 024089b Merge pull request #5415 from Pi-Cla/patch-1
• 3b35dba docs: Add mention of nushell to clap_complete README
• 58469d1 Merge pull request #5405 from epage/docs
• 655d829 docs(derive): Fix ToC links within tutorial chapters
• Additional commits viewable in compare view

Updates anyhow from 1.0.80 to 1.0.81

Release notes

Sourced from anyhow's releases.

1.0.81

• Make backtrace support available when using -Dwarnings (#354)

Commits

• 4aad4ed Release 1.0.81
• 8be9091 Merge pull request #354 from dtolnay/deadcode
• a2eb7dd Make compatible with -Dwarnings
• See full diff in compare view

Updates serde_json from 1.0.114 to 1.0.115

Release notes

Sourced from serde_json's releases.

v1.0.115

• Documentation improvements

Commits

• b1ebf38 Release 1.0.115
• c3dc153 Merge pull request #1119 from titaniumtraveler/pr
• 218770b Explicitly install a Rust toolchain for cargo-outdated job
• 840da8e Fix missing backticks in doc comments
• 3a3f61b Temporarily disable miri on doctests
• 4a0be88 Format regression tests with rustfmt
• d2dbbf7 Ignore dead code lint in tests
• 8e7b37b Merge pull request #1118 from serde-rs/transparent
• a25f6c6 Remove conditional on repr(transparent)
• fedf834 Ignore non_local_definitions false positive in test
• See full diff in compare view

Updates markup5ever from 0.11.0 to 0.12.0

Commits

• 28f2d2f Check formatting and Clippy lints in CI (#520)
• 2294ed0 Make criterion a regular dev-dependency (#519)
• 124821e Remove more unnecessary imports (#521)
• 69eed50 Avoid warnings for duplicate imports (#517)
• 6563511 Fix incorrect Actions workflow expression (#518)
• 16443ce html5ever: prepare 0.26.1 release (#516)
• c044930 Upgrade to rust edition 2021 (#509)
• 9ef751b Upgrade syn to 2.0 (#499)
• ecbd26a Remove redundant FIXME comment (#508)
• aa11b3b Fix parsing of bogus comments after end tags (#507)
• Additional commits viewable in compare view

Updates thiserror from 1.0.57 to 1.0.58

Release notes

Sourced from thiserror's releases.

1.0.58

• Make backtrace support available when using -Dwarnings (#292)

Commits

• df8bffa Release 1.0.58
• 14be209 Merge pull request #292 from dtolnay/deadcode
• 15a1d64 Make compatible with -Dwarnings
• f55a5d2 Ignore mixed_attributes_style clippy lint
• f770921 Resolve assigning_clones clippy lint
• See full diff in compare view

Updates dioxus from 0.4.3 to 0.5.1

Release notes

Sourced from dioxus's releases.

v0.5.0

Dioxus 0.5: Signal Rewrite, Remove lifetimes/unsafe, CSS Hotreloading, 5x Faster Desktop, Asset System, and more!

Read the Full 0.5 release post on the Dioxus blog

The story

---

Here at Dioxus Labs, we have an unofficial rule: only one rewrite per year.

Our last rewrite brought some amazing features: templates, hotreloading, and insane performance. However, don’t be mistaken, rewrites are scary, time consuming, and a huge gamble. We started this new rewrite on January 1st of 2024, completed it by Feburary 1st, and then spent another month and a half writing tests, squashing bugs, and polishing documentation. Rewrites are absolutely not for the faint of heart.

If you’re new here, Dioxus (dye•ox•us) is a library for building GUIs in Rust. Originally, I built Dioxus as a rewrite of Yew with the intention of supporting proper server-side-rendering. Eventually, Dioxus got popular, we got some amazing sponsors, and I went full time. We’ve grown from a team of 1 (me) to a team of 4(!) - pulled entirely from the wonderful dioxus community.

Now, Dioxus is something a little different. Real life, actual companies are shipping web apps, desktop apps, and mobile apps with Dioxus. What was once just a fun little side project powers a small fraction of apps out in the wild. We now have lofty goals of simplifying the entire app development ecosystem. Web, Desktop, Mobile, all end-to-end typesafe, blazing fast, living under one codebase. The dream!

With 0.5 we took a hard look at how Dioxus would need to change to achieve those goals. The request we got from the community was clear: make it simpler, make it robust, make it polished.

What’s new?

---

This is probably the biggest release of Dioxus ever, with so many new features, bug fixes, and improvements that I can’t list them all. We churned over 100,000 lines of code (yes, 100,000+) with over 1,400 commits between 0.4.3 and 0.5.0. Here’s a quick overview:

• Complete rewrite of dioxus-core, removing all unsafe code
• Abandoning use_state and use_ref for a clone-free Signal-based API
• Removal of all lifetimes and the cx: Scope state
• A single, unified launch function that starts your app for any platform
• Asset hotreloading that supports Tailwind and Vanilla CSS
• Rewrite of events, allowing access to the native WebSys event types
• Extension of components with element properties (IE a Link now takes all of <a/> properties)
• Integrated Error Boundaries and Server Futures with Suspense integration
• 5x faster desktop reconciliation and custom asset handlers for streaming bytes
• Streaming server functions and fullstack hotreloading
• Tons of QoL improvements, bug fixes, and more!

Lifetime Problems

---

To make Dioxus simpler, we wanted to remove lifetimes entirely. Newcomers to rust are easily scared off by lifetime issues, and even experienced Rustaceans find wading through obtuse error messages exhausting.

In dioxus 0.1-0.4, every value in a component lives for a 'bump lifetime. This lifetime lets you easily use hooks, props and the scope within event listeners without cloning anything. It was the chief innovation that made Dioxus so much easier to use than Yew when it was released.

... (truncated)

Commits

• 9c5e5f9 Release 0.5.1
• 702509c Fix recycling on component callbacks (#2247)
• 0a32910 Use a VecDequeue instead of a vec for bytes (#2246)
• 633e2a7 Fix memory leak in owner (#2245)
• 44fe2de Fix: memory leak on listeners for elements (#2244)
• 6f3c551 Feat: provide root context as method on virtualdom (#2243)
• 821a650 Fix: requeue events, process events (#2236)
• 4d25e3f fix hydration for non-bubbling events (#2234)
• be99e29 Fixes to autofmt, make it more aggressive (#2230)
• 46b0eeb Implement the "Toggle Developer Tools" menu item in desktop (#2198)
• Additional commits viewable in compare view

Updates dioxus-web from 0.4.3 to 0.5.1

Release notes

Sourced from dioxus-web's releases.

v0.5.0

Dioxus 0.5: Signal Rewrite, Remove lifetimes/unsafe, CSS Hotreloading, 5x Faster Desktop, Asset System, and more!

Read the Full 0.5 release post on the Dioxus blog

The story

---

Here at Dioxus Labs, we have an unofficial rule: only one rewrite per year.

Our last rewrite brought some amazing features: templates, hotreloading, and insane performance. However, don’t be mistaken, rewrites are scary, time consuming, and a huge gamble. We started this new rewrite on January 1st of 2024, completed it by Feburary 1st, and then spent another month and a half writing tests, squashing bugs, and polishing documentation. Rewrites are absolutely not for the faint of heart.

If you’re new here, Dioxus (dye•ox•us) is a library for building GUIs in Rust. Originally, I built Dioxus as a rewrite of Yew with the intention of supporting proper server-side-rendering. Eventually, Dioxus got popular, we got some amazing sponsors, and I went full time. We’ve grown from a team of 1 (me) to a team of 4(!) - pulled entirely from the wonderful dioxus community.

Now, Dioxus is something a little different. Real life, actual companies are shipping web apps, desktop apps, and mobile apps with Dioxus. What was once just a fun little side project powers a small fraction of apps out in the wild. We now have lofty goals of simplifying the entire app development ecosystem. Web, Desktop, Mobile, all end-to-end typesafe, blazing fast, living under one codebase. The dream!

With 0.5 we took a hard look at how Dioxus would need to change to achieve those goals. The request we got from the community was clear: make it simpler, make it robust, make it polished.

What’s new?

---

This is probably the biggest release of Dioxus ever, with so many new features, bug fixes, and improvements that I can’t list them all. We churned over 100,000 lines of code (yes, 100,000+) with over 1,400 commits between 0.4.3 and 0.5.0. Here’s a quick overview:

• Complete rewrite of dioxus-core, removing all unsafe code
• Abandoning use_state and use_ref for a clone-free Signal-based API
• Removal of all lifetimes and the cx: Scope state
• A single, unified launch function that starts your app for any platform
• Asset hotreloading that supports Tailwind and Vanilla CSS
• Rewrite of events, allowing access to the native WebSys event types
• Extension of components with element properties (IE a Link now takes all of <a/> properties)
• Integrated Error Boundaries and Server Futures with Suspense integration
• 5x faster desktop reconciliation and custom asset handlers for streaming bytes
• Streaming server functions and fullstack hotreloading
• Tons of QoL improvements, bug fixes, and more!

Lifetime Problems

---

To make Dioxus simpler, we wanted to remove lifetimes entirely. Newcomers to rust are easily scared off by lifetime issues, and even experienced Rustaceans find wading through obtuse error messages exhausting.

In dioxus 0.1-0.4, every value in a component lives for a 'bump lifetime. This lifetime lets you easily use hooks, props and the scope within event listeners without cloning anything. It was the chief innovation that made Dioxus so much easier to use than Yew when it was released.

... (truncated)

Commits

• 9c5e5f9 Release 0.5.1
• 702509c Fix recycling on component callbacks (#2247)
• 0a32910 Use a VecDequeue instead of a vec for bytes (#2246)
• 633e2a7 Fix memory leak in owner (#2245)
• 44fe2de Fix: memory leak on listeners for elements (#2244)
• 6f3c551 Feat: provide root context as method on virtualdom (#2243)
• 821a650 Fix: requeue events, process events (#2236)
• 4d25e3f fix hydration for non-bubbling events (#2234)
• be99e29 Fixes to autofmt, make it more aggressive (#2230)
• 46b0eeb Implement the "Toggle Developer Tools" menu item in desktop (#2198)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.