adapter-cloudflare@5.0.0 breaks deployment
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20.8k
- Forks
- 2.3k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 156
Description
Describe the bug
After upgrading to @sveltejs/adapter-cloudflare@5.0.0 deployments no longer work, the ./.svelte-kit/cloudflare now depends on ./.svelte-kit/output and cannot resolve external dependencies. (in my case @ts-rest/core).
Reproduction
Deployment using only ./.svelte-kit/cloudflare binaries: https://github.com/trakt/trakt-lite/actions/runs/12734910219/job/35493024100#step:5:68
Deployment with ./.svelte-kit/output unpacked: https://github.com/trakt/trakt-lite/actions/runs/12735478470/job/35494291485#step:6:68
Deployment with @sveltejs/adapter-cloudflare@4.9.0 output: https://github.com/trakt/trakt-lite/actions/runs/12735605634/job/35494549765#step:5:67
Logs
No response
System Info
System:
OS: macOS 15.1.1
CPU: (14) arm64 Apple M3 Max
Memory: 1.29 GB / 36.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.18.0 - ~/.nvm/versions/node/v20.18.0/bin/node
npm: 10.8.2 - ~/.nvm/versions/node/v20.18.0/bin/npm
bun: 1.1.30 - /opt/homebrew/bin/bun
Browsers:
Chrome: 131.0.6778.265
Safari: 18.1.1
Severity
blocking an upgrade
Additional Information
No response
Contributor 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.
Research direction
Start by comparing the deployment workflows linked in the reproduction, focusing on the .svelte-kit/cloudflare and .svelte-kit/output directories and the adapter-cloudflare 4.9.0 versus 5.0.0 outputs. Confirm the affected deployment can use only .svelte-kit/cloudflare while resolving external dependencies such as @ts-rest/core, without requiring .svelte-kit/output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100