-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add build target option to the custom component gradio.config.js
file
#8520
Conversation
🪼 branch checks and previews
Install Gradio from this PR pip install https://gradio-builds.s3.amazonaws.com/bd261008a1ee5945a7d366da69ce026914329800/gradio-4.36.1-py3-none-any.whl Install Gradio Python Client from this PR pip install "gradio-client @ git+https://github.com/gradio-app/gradio@bd261008a1ee5945a7d366da69ce026914329800#subdirectory=client/python" Install Gradio JS Client from this PR npm install https://gradio-builds.s3.amazonaws.com/bd261008a1ee5945a7d366da69ce026914329800/gradio-client-1.1.1.tgz |
gradio.config.js
file
🦄 change detectedThis Pull Request includes changes to the following packages.
With the following changelog entry.
Maintainers or the PR author can modify the PR title to modify this entry.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works 🔥
Two suggestions:
- Add the default build option in the default gradio.config.js so that people know it exists
- Add docs
Nice suggestion @freddyaboulton ! |
what is this 'doc' that you speak of? |
Added the default value to the template and added the options to the configuration section of the |
Lovely! |
I'll be watching you release this fix! Thanks, all. |
Adds
build.target
option to the gradio custom component config options. Defaults to"modules"
which is Vite's default value making this backwards compatible.cc @radames @freddyaboulton
Closes #8416.