---
package: "@webjsdev/cli"
version: 0.9.0
date: 2026-05-25T08:47:54.016Z
commit_count: 2
---
## Breaking

- **Default `webjs dev` / `webjs start` port is now 8080 (was 3000)** ([#97](https://github.com/webjsdev/webjs/pull/97)) [`7c44e6e`](https://github.com/webjsdev/webjs/commit/7c44e6e)

  3000 is heavily contested locally (Next.js, CRA, Express, Flask all
  default there), so newly scaffolded apps now serve on 8080.
  `process.env.PORT` still wins, so deploys that inject `PORT` (Railway,
  Fly, Heroku, etc.) are unaffected.

  **Migration:** to keep the old port, set `PORT=3000` (or pass
  `--port 3000`) when running `webjs dev` / `webjs start`. Scaffolded
  apps need no change.

## Fixes

- **Resolve the @webjsdev/ui registry via the module resolver, not path math** ([#95](https://github.com/webjsdev/webjs/pull/95)) [`f01059b`](https://github.com/webjsdev/webjs/commit/f01059b)

  `webjs create` located the UI registry with `__dirname/../../ui/packages/registry`,
  which assumed @webjsdev/ui was hoisted as a sibling of @webjsdev/cli. That
  broke on non-hoisted layouts (pnpm's isolated linker, `npm install
  --install-strategy=nested`, some CI setups), failing the scaffold. It now
  resolves the registry through `require.resolve`, so `webjs create` works
  regardless of install layout.
