gradio/ui
2022-03-31 14:28:25 -04:00
..
packages change to image3d in directory.ts 2022-03-31 14:28:25 -04:00
.editorconfig
.gitignore
.prettierignore type components with typescript (#545) 2022-02-07 14:34:53 +00:00
.prettierrc.json
global.d.ts type components with typescript (#545) 2022-02-07 14:34:53 +00:00
package-lock.json changes 2022-03-02 22:59:36 +00:00
package.json add model3d output 2022-03-03 21:23:34 -05:00
pnpm-lock.yaml add model3d output 2022-03-03 21:23:34 -05:00
pnpm-workspace.yaml undo pretty format of website 2022-02-14 16:50:15 -05:00
README.md add frontend build to ci as a smoke test (#530) 2022-02-03 10:54:21 +00:00
tsconfig.json formatting fixes 2022-02-16 16:43:46 +00:00
vitest.config.ts add unit tests (#602) 2022-02-14 15:24:04 +00:00

gradio-ui

This folder contains all of the Gradio UI and component source code.

Note: The below assumes you are in the ui directory unless alternative instructions are given.

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 from the ui folder:

pnpm i

This will install the dependencies for all packages within the ui folder and link any local packages

local development

To develop locally, open two browser 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 7863 that the web app is expecting.

Run the web app:

cd ui #move back into ui if you haven't already
pnpm dev

building for production

From the ui folder run the build.

pnpm build

This will create the necessary files in ui/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:

  • Format check (pnpm format:check)
  • Type check (pnpm ts:check)
  • Build as a smoke test (pnpm build)