Repository navigation
fix: allow CommerceKit local development origin - #10
Merged
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
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
http://localhost:5173alongsidehttps://commercekit.toolsProblem
The CCv2 API reference and Playground call the Sandbox directly from the browser. During CommerceKit local development, the Worker returned successful responses without
Access-Control-Allow-Originbecause its source-controlledALLOWED_ORIGINScontained only the production website. Browsers therefore blocked the response fromhttp://localhost:5173.Validation
pnpm run ciDeployment
Cloudflare Workers Builds remains the deployment owner. Merging this PR will publish the updated runtime variable through the existing deployment; no manual deployment, wildcard CORS rule, credential change, or website proxy is required.