@webjsdev/server 0.7.3

Changes

• startServer default port and OAuth fallback origin moved to 8080 (#97) 7c44e6e

  startServer({ appDir }) without an explicit port now defaults to 8080
  (was 3000), matching the new @​webjsdev/cli default, and the OAuth
  no-request fallback origin moved from localhost:3000 to localhost:8080.
  process.env.PORT and an explicit port option still win. The recommended
  createRequestHandler embedding path is unaffected (the host server owns
  the port there).

@webjsdev/cli 0.9.1

Fixes

• sync scaffold dark mode so ui- components follow the theme* (#101) f0a1fa1

  • fix(cli): sync scaffold dark mode so ui-* components follow the theme

  The default scaffold shipped two unsynced theme systems: the editorial
  chrome tokens (--fg/--bg) toggled via a data-theme attribute, while

@webjsdev/cli 0.9.0

Breaking

• Default webjs dev / webjs start port is now 8080 (was 3000) (#97) 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) 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.

@webjsdev/ui 0.3.2

Fixes

• include packages/registry in npm package files a23b43e

@webjsdev/cli 0.8.6

Fixes

• fail loudly when @​webjsdev/ui registry is missing at scaffold time 6ac4a0d
  The scaffold reads UI component sources directly from the installed
  @​webjsdev/ui's packages/registry/ directory, then generates an
  app/page.ts that imports the copied files. Until the previous commit,
  if the registry wasn't on disk, the copy helpers silently no-op'd and

@webjsdev/cli 0.8.5

Fixes

• scaffold's next-steps banner now points at npx webjsdev ui ... instead of the broken npx webjs ui ... The bare webjs npm name is owned by an unrelated package, so npx webjs <cmd> would fetch THAT package rather than ours when run outside a scaffolded project. Switched both banner lines (the api-template hint and the non-api Optional line) to npx webjsdev <cmd>, our unscoped CLI alias. Behaviour matches @​webjsdev/cli exactly via npx's single-bin fallback, with no scope to type.

@webjsdev/cli 0.8.4

Features

• reorder webjs create output so the run command is the last thing on screen Previously the "Next steps:" banner printed BEFORE the AI-driven-development guidance and the for-AI-agents bullet list, which together push the actionable cd <name> && <pm> run dev line off the visible terminal. After this change, the AI guidance prints first (long reading material, scrolls past), the install step runs, then the run command lands as the final output. Users land on the actionable command without scrolling.

@webjsdev/cli 0.8.3

Breaking

• revert the wjs bin alias introduced in 0.8.2 The bin map is back to the original single webjs entry. Only webjs is provided as a command name going forward; users who want npx <shortname> discoverability for the scaffolder use create-webjs-app, and users who want the CLI under an unscoped install path use the webjsdev package (which also ships only webjs as its bin).
  Migration note for anyone who installed @​webjsdev/cli@​0.8.2 and used the wjs command: replace wjs <cmd> calls with webjs <cmd>. The command name is the only change; behaviour is identical.

@webjsdev/cli 0.8.2

Features

• ship wjs as a bin alias in @​webjsdev/cli Adds "wjs": "bin/webjs.js" alongside the existing "webjs" entry, so npm i -g @​webjsdev/cli now puts both commands on PATH from a single install. Same script either way; the long form matches the documentation, the short form saves keystrokes. Existing scaffold templates, npm run dev, and AI-agent docs that reference webjs <cmd> continue to work unchanged.

@webjsdev/ui 0.3.1

Breaking

• Rescope from @​webjskit/ui to @​webjsdev/ui (#62)
  The npm scope now matches the canonical webjs.dev domain (and the @​webjsdev org we own on npm). Functionally identical to the prior @​webjskit/ui@​0.3.0 publish, no component or CLI behavior change. The webjs ui add command now writes imports from @​webjsdev/core into added components. Update existing lib/utils/ui.ts and any other manually-imported references from @​webjskit/ui to @​webjsdev/ui. The legacy @​webjskit/* packages stay installable, but will be marked deprecated on the registry to redirect new installers here.