- resample the 3MB trending background to a 97KB webp and serve a frozen recommend banner from the E2E stub so the benchmark covers the carousel - show the on-page filtered count in template search and redirect out-of-range pages to the last available page - localize the carousel controls across all 24 locales and replace the i18n type casts with typed selectors - surface Marketplace API failures with a retry action instead of rendering them as empty results - use iconify marks for the hero decorations, share the carousel page-size hook to avoid a hydration mismatch, move banner types into @dify/contracts, scope the Cmd+K shortcut to the standalone platform, point the embedded logo at /marketplace, pass resolvedTheme to the detail dialogs, and reveal the detail iframe after a loading timeout Co-authored-by: Cursor <cursoragent@cursor.com> |
||
|---|---|---|
| .. | ||
| __mocks__ | ||
| __tests__ | ||
| .storybook | ||
| .vscode | ||
| app | ||
| assets | ||
| bin | ||
| config | ||
| constants | ||
| context | ||
| docker | ||
| docs | ||
| features | ||
| hooks | ||
| i18n | ||
| i18n-config | ||
| models | ||
| next | ||
| plugins | ||
| public | ||
| scripts | ||
| service | ||
| test | ||
| themes | ||
| types | ||
| utils | ||
| .env.example | ||
| .gitignore | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| dev-proxy.config.ts | ||
| Dockerfile | ||
| Dockerfile.dockerignore | ||
| env.ts | ||
| global.d.ts | ||
| instrumentation-client.ts | ||
| next.config.ts | ||
| oxlint.unused.config.json | ||
| package.json | ||
| postcss.config.mjs | ||
| proxy.ts | ||
| README.md | ||
| tsconfig.json | ||
| tsslint.config.ts | ||
| vite.config.ts | ||
| vitest.browser.config.ts | ||
| vitest.browser.setup.ts | ||
| vitest.setup.ts | ||
Dify Frontend
This is a Next.js application with vinext as the default local development server.
Getting Started
Run by source code
The required Node.js and pnpm versions are pinned by the repository root .nvmrc and packageManager field. Vite+ is also available for repository checks and tests; use its official documentation as the installation reference.
Run the following commands from the repository root.
First, install the dependencies:
pnpm install
Note
JavaScript dependencies are managed by the workspace files at the repository root:
package.json,pnpm-lock.yaml,pnpm-workspace.yaml, and.nvmrc. Install dependencies and run the commands below from the repository root.
Then, configure the environment variables.
Create web/.env.local and copy the contents from web/.env.example.
Modify the values of these environment variables according to your requirements:
cp web/.env.example web/.env.local
Important
- When the frontend and backend run on different subdomains, set NEXT_PUBLIC_COOKIE_DOMAIN=1. The frontend and backend must be under the same top-level domain in order to share authentication cookies.
- It's necessary to set NEXT_PUBLIC_API_PREFIX and NEXT_PUBLIC_PUBLIC_API_PREFIX to the correct backend API URL.
Finally, start the default development stack from the repository root. This runs vinext and the local API proxy together:
pnpm dev
Use pnpm -C web dev only when you specifically need the Next.js development server without the default vinext process. Proxy environment variables are documented in web/.env.example; route ownership remains in web/dev-proxy.config.ts.
Open http://localhost:3000 with your browser to see the result.
You can start editing the files under web/app.
The page auto-updates as you edit the file.
Deploy
Deploy on server
First, build the app for production:
pnpm -C web run build
Then, start the server:
pnpm -C web run start
If you build the Docker image manually, use the repository root as the build context:
docker build -f web/Dockerfile -t dify-web .
If you want to customize the host and port:
pnpm -C web run start --port=3001 --host=0.0.0.0
Storybook
This project uses Storybook for UI component development.
To start the storybook server, run:
pnpm -C web storybook
Open http://localhost:6006 with your browser to see the result.
Lint Code
If your IDE is VSCode, rename .vscode/settings.example.json to .vscode/settings.json for lint code setting.
Then follow the Lint Documentation to lint the code.
Test
We use Vitest and React Testing Library for Unit Testing.
📖 Frontend Testing Guide: See web/docs/test.md for the canonical testing policy and workflow.
Important
As we are using Vite+, the
vitestcommand is not available. Please make sure to run tests withvpcommands. For example, usenpx vp testinstead ofnpx vitest.
Run test:
cd web
vp test run
If a test fails only in CI, inspect the failing job and reproduce it locally when possible. A rerun can help identify a flaky test, but it does not replace diagnosing or reporting the failure.
Documentation
Visit https://docs.dify.ai to view the full documentation.
Community
The Dify community can be found on Discord community, where you can ask questions, voice ideas, and share your projects.