2b127b73ac
Currently translated at 82.7% (417 of 504 strings) Co-authored-by: Tom <tom.fouthier@gmail.com> Translate-URL: https://hosted.weblate.org/projects/invokeai/web-ui/fr/ Translation: InvokeAI/Web UI |
||
---|---|---|
.. | ||
.husky | ||
.yarn/releases | ||
dist | ||
patches | ||
public/locales | ||
src | ||
__init__.py | ||
.babelrc | ||
.eslintignore | ||
.eslintrc.js | ||
.gitignore | ||
.prettierignore | ||
.prettierrc.js | ||
.yarnrc | ||
.yarnrc.yml | ||
favicon.ico | ||
index.d.ts | ||
index.html | ||
package.json | ||
README.md | ||
stats.html | ||
tsconfig.json | ||
tsconfig.node.json | ||
vite.config.ts | ||
yarn.lock |
InvokeAI Web UI
The UI is a fairly straightforward Typescript React app. The only really fancy stuff is the Unified Canvas.
Code in invokeai/frontend/web/
if you want to have a look.
Details
State management is Redux via Redux Toolkit. Communication with server is a mix of HTTP and socket.io (with a custom redux middleware to help).
Chakra-UI for components and styling.
Konva for the canvas, but we are pushing the limits of what is feasible with it (and HTML canvas in general). We plan to rebuild it with PixiJS to take advantage of WebGL's improved raster handling.
Vite for bundling.
Localisation is via i18next, but translation happens on our Weblate project. Only the English source strings should be changed on this repo.
Contributing
Thanks for your interest in contributing to the InvokeAI Web UI!
We encourage you to ping @psychedelicious and @blessedcoolant on Discord if you want to contribute, just to touch base and ensure your work doesn't conflict with anything else going on. The project is very active.
Dev Environment
Install node and yarn classic.
From invokeai/frontend/web/
run yarn install
to get everything set up.
Start everything in dev mode:
- Start the dev server:
yarn dev
- Start the InvokeAI UI per usual:
invokeai --web
- Point your browser to the dev server address e.g.
http://localhost:5173/
Production builds
For a number of technical and logistical reasons, we need to commit UI build artefacts to the repo.
If you submit a PR, there is a good chance we will ask you to include a separate commit with a build of the app.
To build for production, run yarn build
.