Fix custom component reload mode#12968
Merged
freddyaboulton merged 4 commits intomainfrom Mar 6, 2026
Merged
Conversation
Collaborator
🪼 branch checks and previews
Install Gradio from this PR Install Gradio Python Client from this PR Install Gradio JS Client from this PR |
Collaborator
🦄 change detectedThis Pull Request includes changes to the following packages.
✅ Changeset approved by @freddyaboulton
|
pngwn
reviewed
Mar 6, 2026
| let runtime = $derived( | ||
| (await node.runtime) as { | ||
| mount: typeof import("svelte").mount; | ||
| umount: typeof import("svelte").unmount; |
pngwn
approved these changes
Mar 6, 2026
Member
pngwn
left a comment
There was a problem hiding this comment.
This looks great. Thanks for the clean fix @freddyaboulton!
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.
Description
The problem was that the custom component was only being mounted once so prop updates were not being propagated down to the component. So my fix was to modify the
$effectin MountCustomComponent. Also, instead of using onDestroy, I am returning a function from $effect to do the cleanup.Closes: #12965
AI Disclosure
We encourage the use of AI tooling in creating PRs, but the any non-trivial use of AI needs be disclosed. E.g. if you used Claude to write a first draft, you should mention that. Trivial tab-completion doesn't need to be disclosed. You should self-review all PRs, especially if they were generated with AI.
🎯 PRs Should Target Issues
Before your create a PR, please check to see if there is an existing issue for this change. If not, please create an issue before you create this PR, unless the fix is very small.
Not adhering to this guideline will result in the PR being closed.
Testing and Formatting Your Code
PRs will only be merged if tests pass on CI. We recommend at least running the backend tests locally, please set up your Gradio environment locally and run the backed tests:
bash scripts/run_backend_tests.shPlease run these bash scripts to automatically format your code:
bash scripts/format_backend.sh, and (if you made any changes to non-Python files)bash scripts/format_frontend.sh