Update crate thiserror and others #505
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Moved thiserror up into the root workspace so I only have to bump the version to 2.0 once. * Updated/Fixed deprecated fn names.
…zyLock It Fixed this build error error: package `once_cell v1.21.3` cannot be built because it requires rustc 1.65 or newer, while the currently active rustc version is 1.64.0
error: package `tracing-core v0.1.34` cannot be built because it requires rustc 1.65.0 or newer, while the currently active rustc version is 1.64.0
Bumped rust-version to 1.71.1 error: package `bumpalo v3.19.0` cannot be built because it requires rustc 1.71.1 or newer, while the currently active rustc version is 1.64.0 Bumped this github action - uses: jetli/trunk-action@v0.4.0 + uses: jetli/trunk-action@v0.5.1 BugFix -#[cfg(feature = "browser_test")] +#[cfg(feature = "browser-test")]
Bumped rust-version to 1.82 error: package `icu_normalizer_data v2.0.0` cannot be built because it requires rustc 1.82 or newer, while the currently active rustc version is 1.71.1
However, as of January 2024, the WASI standard was rebased on the Component Model, leading to the release of WASIp2, which is now referred to as wasm32-wasip2. The wasm32-wasi target was renamed to wasm32-wasip1 to avoid confusion with the new target.
because if there are any incompatibilities between version numbers
it is difficult to debug.
[workspace.dependencies]
-thiserror = { version = "2.0" }
+thiserror = "2.0"
+wasm-bindgen-futures = "0.4.4"
+wasm-bindgen = "0.2"
+wasm-bindgen-test = "0.3.4"
+js-sys = "0.3.77"
Author
|
Of the three remaining failure, it looks like firefox is reaching out of the network to preform some ad blocking funciton ... The CORS policy is blocking a "fetch" request for a URL on the internet .. and failing Hmm not sure how to fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I like this project ... it is really useful.
In a way this is a field report from a upstream user.
The leptos framework makes extensive use of gloo
I have a application based on leptos ..
and am tracking down why there are many duplicate versions version of certain crates being built.
( duplicate but with different version numbers )
I want to upgrade "thiserror" to a modern version
This is open source, so for crates I depend on, I am happy to go a bit further and do all the basic maintence
I can see, So I did the following