Repository navigation
Are backend-only apps supported? #3068
|
Im looking for a unified toolchain for backend-only apps, like for Express and Hono. Im trying to migrate my microservices from Deno to Node, and this would be really appreciated! |
Answered by
KevinAndrewDong
Oct 27, 2026
Replies: 2 comments 1 reply
|
It should be supported. If you encounter any issues, please feel free to let us know at any time. |
0 replies
|
Yes for toolchain (env, install, check, test, run, pack). Not as a first-class “backend-only Recommended pattern (Hono/Express): {
"scripts": {
"dev": "tsx watch src/server.ts",
"start": "node dist/server.js",
"check": "vp check",
"test": "vp test"
}
}vp install
vp run dev # your API (Bun/Node/tsx) — not `vp dev`
vp check
vp testMonorepo (API + optional web): # packages/api: "dev": "tsx watch src/index.ts"
# packages/web: "dev": "vp dev"
vp run -r --parallel --filter @repo/api --filter @repo/web devSo: migrate Deno → Node services with Vite+ for lint/test/tasks; keep the HTTP server as a normal Node script under |
1 reply
Answer selected by
fengmk2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yes for toolchain (env, install, check, test, run, pack). Not as a first-class “backend-only
vp dev” product yet (see open requests for pure Node watch without port 5173).Recommended pattern (Hono/Express):
{ "scripts": { "dev": "tsx watch src/server.ts", "start": "node dist/server.js", "check": "vp check", "test": "vp test" } }Monorepo (API + optional web):
So: migrate Deno → Node services with Vite+ for lint/test/tasks; keep the HTTP server …