You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/tutorials/nodejs-tools/vite.md
+2-15Lines changed: 2 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -67,22 +67,9 @@ An important first check is that vite is accessible via `https://your-ddev-proje
67
67
68
68
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
69
69
70
-
## Add-On: ddev-viteserve
70
+
## Codespaces
71
71
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=.`.
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.
0 commit comments