Fix Cloudflare worker import paths on Windows#6757
Merged
vimtor merged 1 commit intoanomalyco:devfrom Apr 17, 2026
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Cloudflare Worker builds on Windows broke because the absolute handler path was embedded in generated stdin JS using double-quoted string literals. Backslashes were interpreted as escapes, corrupting the path. Use
filepath.ToSlashon that path before interpolating it into the import/export source inpkg/runtime/worker/worker.go.Related
Fixes #6756
Test plan
go test ./pkg/runtime/worker/...sst devor deploy withhome: "cloudflare"and a nested handler path; confirm bundling succeeds.