allow custom component authors to provide custom vite plugins and svelte preprocessors

[pngwn]

Description

Please include a concise summary, in clear English, of the changes in this pull request. If it closes an issue, please mention it here.

Closes #8044. Closes #7927. Closes #7006.

🎯 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.

Tests

1. PRs will only be merged if tests pass on CI. To run the tests locally, please set up your Gradio environment locally and run the tests: bash scripts/run_all_tests.sh

2. You may need to run the linters: bash scripts/format_backend.sh and bash scripts/format_frontend.sh

[gradio-pr-bot]

🪼 branch checks and previews

•	Name	Status	URL
	Spaces	ready!	Spaces preview
	Website	ready!	Website preview
	Storybook	ready!	Storybook preview
🦄	Changes	detected!	Details

---

Install Gradio from this PR

pip install https://gradio-builds.s3.amazonaws.com/4aea4918958e72f36eec9b3c7de86f34d9aa6054/gradio-4.27.0-py3-none-any.whl

Install Gradio Python Client from this PR

pip install "gradio-client @ git+https://github.com/gradio-app/gradio@4aea4918958e72f36eec9b3c7de86f34d9aa6054#subdirectory=client/python"

[gradio-pr-bot]

🦄 change detected

This Pull Request includes changes to the following packages.

Package	Version
@gradio/preview	minor
gradio	minor
gradio_test	minor

• Maintainers can select this checkbox to manually select packages to update.

With the following changelog entry.

allow custom component authors to provide custom vite plugins and svelte preprocessors

Maintainers or the PR author can modify the PR title to modify this entry.

Something isn't right?

• Maintainers can change the version label to modify the version bump.
• If the bot has failed to detect any changes, or if this pull request needs to update multiple packages to different versions or requires a more comprehensive changelog entry, maintainers can update the changelog file directly.

[pngwn]

We need to do something else.

[pngwn]

Important

Outdated! Updated instructions.

To test this:

run pnpm build from the root.

Copy paste this code in to the js/preview/test/test/frontend/gradio.config.js:

import tailwindcss from "@tailwindcss/vite";

export default {
	plugins: [tailwindcss()]
};

Add this file in the frontend dir:

main.css:

@import "tailwindcss";

Add this code to Index.svelte:

import './main.css';

Run this command in the frontend dir:

pnpm add -D tailwindcss@next @tailwindcss/vite@next

cd back into test/test and run:

gradio cc install --npm-install="pnpm i"
gradio cc dev

[pngwn]

tbh i'll just push these changes

[pngwn]

New instructions:

pnpm i
ppm build
cd js/preview/frontend/test/test
gradio cc install --npm-install="pnpm i"
gradio cc dev

then visit the URL shown in the console.

[freddyaboulton]

Awesome, I copied some random code from the internet and it just works

FYI: going to start accepting payments in my gradio apps 😂

[freddyaboulton]

Nice @pngwn ! Let's please write some docs for this in the frontend guide: https://www.gradio.app/guides/frontend

I still think we should provide an empty gradio.config.js file in the create command so that users know about it without having to use the guides. Maybe we include some commented out code like "to add tailwind, add the following"

[pngwn]

Good idea. Will update.

[pngwn]

@freddyaboulton I have done the following:

• we now generate a gradio.config.js as part of the create command. I haven't 'filled it in' atm. Its kinda noisy with all the comments so not sure if that is best, but don't feel strongly.
• Added a section of custom configuration to the frontend guide: https://gradio-q7zldhffx-hugging-face.vercel.app/main/guides/frontend#custom-configuration

[freddyaboulton]

Need to close this codeblock

[pngwn]

ah nice catch.

[freddyaboulton]

Docs changes look good to me @pngwn !