Skip to content

Commit 8cd143c

Browse files
committed
chore: update vite infos
1 parent b293d88 commit 8cd143c

File tree

1 file changed

+2
-15
lines changed

1 file changed

+2
-15
lines changed

docs/tutorials/nodejs-tools/vite.md

Lines changed: 2 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -67,22 +67,9 @@ An important first check is that vite is accessible via `https://your-ddev-proje
6767

6868
Afterwards your CMS / PHP frameworks needs to be configured accordingly, see above. The official docs for this can be found here: https://vitejs.dev/guide/backend-integration.html
6969

70-
## Add-On: ddev-viteserve
70+
## Codespaces
7171

72-
There is a new plugin for DDEV called [viteserve](https://github.com/torenware/ddev-viteserve) by torenware. It runs vite in the background and has support for package managers npm, yarn and pnpm (default).
73-
74-
You can configure it (after installation) via `.ddev/.env`, here is an example for having vite config in a subfolder. If you want to use the project root, use `VITE_PROJECT_DIR=.`.
75-
76-
```bash
77-
# start vite
78-
VITE_PROJECT_DIR=wp-content/themes/twentytwentytwo-child/
79-
VITE_PRIMARY_PORT=5173
80-
VITE_SECONDARY_PORT=5273
81-
VITE_JS_PACKAGE_MGR=npm
82-
# end vite
83-
```
84-
85-
See full documentation for DDEV viteserve here: https://github.com/torenware/ddev-viteserve
72+
Codespaces works differently since there is no ddev router used. Therefore exposing ports via `.ddev/config.yaml` will not work. You need to use docker compose file again, see e.g. https://github.com/mandrasch/ddev-craftcms-vite/blob/main/.devcontainer/postCreateCommand.sh for a workaround.
8673

8774
## Connect with the community 🤗
8875

0 commit comments

Comments
 (0)