Abubakar Abid
f0a2d9d70b
The functional workflow installed demo/outbreak_forecast/requirements.txt
(numpy, matplotlib, bokeh, plotly, altair) and demo/stream_video_out/
requirements.txt (opencv-python) before the browser tests. But the only
packages there not already in test/requirements.txt — bokeh, plotly,
opencv-python — are used solely by those two demos, whose specs are entirely
skipped: outbreak_forecast.spec.ts is all `test.fixme`, and
stream_video_out.spec.ts is all `test.skip` ("Not supported in CI"). Those
apps are never launched by the suite, so the deps were never exercised.
Drop the "install dependencies for specific tests" step and the matching
lines in the contributor docs (js/README.md, CONTRIBUTING.md). Removes the
uncached external installs from the e2e path — a setup burden and extra
failure point — with no change to which tests actually run.
Closes #11310
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2.4 KiB
gradio-ui
This folder contains all of the Gradio UI and component source code.
setup
This folder is managed as 'monorepo' a multi-package repository which make dependency management very simple. In order to do this we use pnpm as our package manager.
Make sure pnpm is installed by following the installation instructions for your system.
You will also need node which you probably already have
running the application
Install all dependencies:
pnpm i
This will install the dependencies for all packages and link any local packages
local development
To develop locally, open two terminal tabs from the root of the repository.
Run the python test server, from the root directory:
cd demo/kitchen_sink
python run.py
This will start a development server on port 7860 that the web app is expecting.
Run the web app:
pnpm dev
building for production
Run the build:
pnpm build
This will create the necessary files in js/app/public and also in gradio/templates/frontend.
quality checks
The repos currently has two quality checks that can be run locally and are run in CI.
formatting
Formatting is handled by prettier to ensure consistent formatting and prevent style-focused conversations. Formatting failures will fails CI and should be reoslve before merging.
To check formatting:
pnpm format:check
If you have formatting failures then you can run the following command to fix them:
pnpm format:write
type checking
We use TypeScript to provide static types to javascript code. These checks are also run in CI.
to typecheck the code:
pnpm ts:check
ci checks
Currently the following checks are run in CI:
static checks
- Format check (
pnpm format:check) - Build css (
pnpm css) - Build client (
pnpm build) - Type check (
pnpm ts:check) - Unit tests (
pnpm test:run)
functional test
pnpm exec playwright install chromium firefox
pnpm exec playwright install-deps chromium firefox
pnpm --filter @gradio/utils --filter @gradio/theme package
pnpm test:browser:full