fix(wrangler): Fix type generation inheritable bindings#12746
Merged
Conversation
🦋 Changeset detectedLatest commit: 8774547 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
create-cloudflare
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-editor-shared
wrangler
commit: |
Contributor
|
✅ All changesets look good |
Contributor
|
Codeowners approval required for this PR:
Show detailed file reviewers |
jamesopstad
reviewed
Mar 6, 2026
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.
Fixes #12737.
Currently the type generation requires a binding to be defined at all levels (top-level and all named environments) in order for the generated binding type to be marked as required.
However, as pointed out in the linked issue, some bindings, namely the assets binding, are inheritable (Docs) and allow for you to define the binding once at the top-level and have it applied to all named environments. As such, the type generation to account for this.
A picture of a cute animal (not mandatory, but encouraged)