Server crash at startup

[JessenReinhart]

Expectation
User can start the server

Actual
Server crashes at startup

Tried workaround
Navigate to vansrouter/app in node_modules, then run npm install @next/env
server then runs, however the previous error appeared again

Error Log:

vansrouter
⚠ Network-exposed: reachable at http://10.132.10.74:20128 (bound 0.0.0.0). Use --host 127.0.0.1 for local-only.

⚠️  Server exited (code=1). Restarting in 1s... (1/2)

--- Server crash log ---
node:internal/modules/cjs/loader:1424
  throw err;
  ^

Error: Cannot find module '@next/env'
Require stack:
- C:\npm-global\node_modules\vansrouter\app\node_modules\next\dist\server\config.js
- C:\npm-global\node_modules\vansrouter\app\node_modules\next\dist\server\next.js
- C:\npm-global\node_modules\vansrouter\app\server.js
- C:\npm-global\node_modules\vansrouter\app\custom-server.js
    at Module.<anonymous> (node:internal/modules/cjs/loader:1421:15)
    at C:\npm-global\node_modules\vansrouter\app\node_modules\next\dist\server\require-hook.js:68:36
    at defaultResolveImpl (node:internal/modules/cjs/loader:1059:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1064:22)
    at Module._load (node:internal/modules/cjs/loader:1227:37)
    at TracingChannel.traceSync (node:diagnostics_channel:328:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:245:24)
    at Module.<anonymous> (node:internal/modules/cjs/loader:1504:12)
    at mod.require (C:\npm-global\node_modules\vansrouter\app\node_modules\next\dist\server\require-hook.js:79:28)
    at require (node:internal/modules/helpers:152:16) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'C:\\npm-global\\node_modules\\vansrouter\\app\\node_modules\\next\\dist\\server\\config.js',
    'C:\\npm-global\\node_modules\\vansrouter\\app\\node_modules\\next\\dist\\server\\next.js',

[Vanszs]

halo mas, saya coba cari referensi dulu untuk error ini, mungkin nanti bisa saya buatkan khusus branch untuk try n error issue ini, maaf atas ketidaknyamanannya

[Vanszs]

Hi, thanks for the report.

This should be fixed in v0.8.5-beta.1. The root cause was not an assumption — we reproduced it locally.

What we found

next/dist/server/config.js requires @next/env:

grep -n "require.*@next/env" node_modules/next/dist/server/config.js
# 41:const _env = require("@next/env")

But after the CLI build, @next/env was missing from cli/app/node_modules because ensureModuleInBundle() only looked at flat node_modules paths. In pnpm workspaces, transitive deps like @next/env live inside node_modules/.pnpm/next@.../node_modules/, so the bundler could not find it.

Fix

• cli/scripts/build-cli.js: resolve the real next directory and look for the target package as a sibling in the pnpm virtual store, so @next/env is copied into the standalone app.
• Added .github/workflows/release-beta.yml to publish beta npm tag and GHCR beta tag without overwriting stable latest.
• Main release workflow now skips tags containing -beta.

Verified

• npm install -g vansrouter@0.8.5-beta.1 ✅
• require('.../next/dist/server/config.js') loads without MODULE_NOT_FOUND ✅
• docker pull ghcr.io/vanszs/vansrouter:0.8.5-beta.1 ✅
• /api/health returns {"ok":true} on the beta Docker image ✅

Please try

# npm global install (beta tag — does not trigger stable auto-update)
npm install -g vansrouter@0.8.5-beta.1
vansrouter

or

# Docker
docker pull ghcr.io/vanszs/vansrouter:0.8.5-beta.1
docker run -d \
  -p 20128:20128 \
  -v "$HOME/.9router:/app/data" \
  -e DATA_DIR=/app/data \
  --name vansrouter-beta \
  ghcr.io/vanszs/vansrouter:0.8.5-beta.1

or build from branch fix/cli-missing-next-env.

Please let us know if the startup crash is gone. Do not close this issue until we confirm it works on your side.

[Vanszs]

@JessenReinhart bisa dicoba versi beta ini mas? nanti mas kabari saja update nya

[JessenReinhart]

berhasil login, cuma sekarang ada problem baru.

ketika mau add model utk OpenCode, dia error

[Vanszs]

Halo @JessenReinhart, terima kasih sudah mencoba v0.8.5-beta.1.

Fix startup CLI di beta.1 hanya menyentuh cli/scripts/build-cli.js (bundling @next/env). Seharusnya tidak berpengaruh ke dashboard atau import custom model.

Untuk memastikan penyebab error "failed to add custom model", mohon info tambahan:

1. Errornya muncul sebagai alert/popup di browser, atau di server log / browser console?
2. Buka DevTools → Network, ulangi aksi "Add Model", lalu share response body dari request yang gagal (biasanya POST /api/models/custom atau POST /api/cli-tools/opencode-settings).
3. Kalau ada baris log server seperti Error adding custom model: ..., mohon paste di sini.

Dari sisi kode, POST /api/models/custom mengembalikan Failed to add custom model hanya ketika layer DB throw. Tes DB terkait (tests/unit/db-sqlite-vs-lowdb.test.js,
tests/unit/db-concurrent.test.js) lulus di lokal, jadi kemungkinan ini environment-specific (misal: SQLite driver mana yang dipakai binary yang sedang berjalan, permission file di
data dir, atau DB schema yang stale).

Mohon dibantu detail network/log-nya supaya bisa saya pinpoint.