Add Rust Worker project support to `cf dev`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust, typescript
Research direction
Start from the cf dev entry point and the project metadata used to identify a Rust Worker. Define the documented Rust Worker fixture and validate toolchain and package requirements before covering build, runtime, option forwarding, reload, failure reporting, and shutdown. Add automated tests for startup, reload, build failure, and shutdown, then verify the fixture meets the acceptance criteria.
Written by the indexing model from the issue text.
Description
Summary
Define and implement a supported local-development path for Rust Worker projects.
Scope
- Detect an agreed Rust Worker project shape from public project metadata.
- Validate required toolchain and package versions.
- Build the Worker and start the supported local runtime.
- Forward relevant
cf devoptions, including mode, bindings, and persistence. - Report build and runtime failures with actionable guidance.
- Shut down child processes cleanly on exit and cancellation.
Acceptance criteria
- A documented Rust Worker fixture starts with
cf dev. - Source changes trigger the expected rebuild/reload behavior.
- Bindings and environment configuration reach the Worker correctly.
- Missing or incompatible tooling produces a clear installation or upgrade message.
- Automated tests cover startup, reload, build failure, and shutdown.
- Dominant language
- TypeScript
- Stars
- 853
- Forks
- 42
- Avg merge
- 17h 57m
- Merged PRs (30d)
- 146
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudflare/cf
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cloudflare/cf#344 ·
Maintainers usually reply within 1 day
-
upstream
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/cf#262 ·
Maintainers usually reply within 1 day
-
`cf dev` rejects `--port` and `--host` for Vite projects, including the `cf init` templatePossibly taken @jamesopstad claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/cf#223 · 2 assignees ·
Maintainers usually reply within 1 day
-
upstream
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cloudflare/cf#179 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
cloudflare/cf#347 ·
Maintainers usually reply within 1 day
Similar issues
-
freshness freshness:observed-only
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
thoroc/context-radar#280 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
documentation story
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug category:billing priority:p3 track:fast
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LanternOps/breeze#9223 ·
Maintainers usually reply within 1 day