-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃摑 caveat when upgrading to worker 0.0.18 #400
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might make sense to note that we require 2021 edition at the top as well, but this looks good for now
@kflansburg I believe this advice may be outdated or not clear enough
This errors with "Additional properties are not allowed ('package' was unexpected)" and does nothing to remedy the original problem. Any help would be amazing! |
Your [package]
name = "backend"
main = "build/worker/shim.mjs"
compatibility_date = "2024-05-22"
edition = "2021"
[build]
command = "cargo install -q worker-build && worker-build --release" |
@avsaase The original PR says wrangler.toml
My cargo.toml has this and its not compiling mio with same error set as above. We may need to reopen this or create a new thread unless im still missing something. |
That can't be correct. My example isn't either though. The edition field should be added to the |
Here is my projects Toml file.
I also have resolver = "2" set in the Cargo.toml workspace which some other issues related have suggesed. Resuts in
|
I suspect axum = { version = "0.7", default-features = false } You may need to manually re-enable some of the features listed here. |
@avsaase thank you that fixed the problem, though I was still having issues with socket2 haha, I'll have to end up going to a non wasm solution unfortunately thank you for the help! |
Context
We (@kodadot) are huge fans of Cloudflare and Workers and we have a ton of workers in the prod (Rust / TS).
As anyone would upgrade to latest version they would meet this very scary error
The only mention I found was in Cloudlfare's discord