Skip to content

Some commands in DEVELOPING.md don’t exist; Visual Editor dev server opens unexpected page #6789

@aniruddhha

Description

@aniruddhha

Hi team 👋 — I’m setting up a local dev environment to contribute and ran into two problems:

1) DEVELOPING.md commands not found

The doc mentions these shortcuts:

npm run w     # bring up Breadboard Web UI
npm run d     # start doc site server
npm run s     # start board server + Web UI

But these scripts aren’t present in the root package.json on main in my checkout. Running them yields:

npm ERR! Missing script: "w"
npm ERR! Missing script: "d"
npm ERR! Missing script: "s"

Question: Have these scripts been renamed/moved/removed? If so, could the docs be updated with the current equivalents (or the workspace targets I should use)?

2) Visual Editor starts but browser opens an unexpected page (/landing/)

I can start the Visual Editor like this:

# from repo root
npm run dev -w packages/visual-editor
# or (UI-only via vite)
npm exec -w @breadboard-ai/visual-editor vite -- --host 127.0.0.1 --port 3001 --strictPort --open

The dev server starts successfully (Vite prints a local URL), but the browser opens an unexpected page that looks unrelated to Breadboard and redirects to /landing/. Two screenshots:

  • Full page:
    Image

  • Redirect snippet / location bar:
    Image

Notes / what I tried

  • Verified the dev server is running and serving on the reported port.
  • Opening the root path (/) still redirects to /landing/.
  • Tried alternate ports (e.g., 3001, 5174) and hosts (localhost vs 127.0.0.1).
  • (Suspicion) This might be a service-worker from a different app that previously used the same origin (host+port) and is intercepting navigation.

Questions:

  1. What is the canonical way to launch the Visual Editor today (equivalent to npm run w)?
    • Should I use npm run dev -w @breadboard-ai/visual-editor or the @breadboard-ai/unified-server script?
  2. Does the Visual Editor expect a specific route (root /), or is there a landing route that should load first?
  3. Are there any service-worker registrations in dev that could cause redirect behavior? (If not, I’ll purge SW/site data locally as a workaround.)

Environment

  • OS: macOS (Apple Silicon/Intel)
  • Node: via nvm (from repo’s .nvmrc)
  • npm: (from npm -v)
  • Branch: main (fresh clone / up to date with upstream)
  • Install: npm ci

Expected vs Actual

  • Expected: A working dev command that opens the Breadboard Visual Editor at the root path.
  • Actual:
    • Docs reference npm run w / d / s scripts that don’t exist.
    • Visual Editor dev server runs, but browser opens/redirects to an unrelated /landing/ page.

Anything I can do to help

  • I can submit a PR to update DEVELOPING.md once I know the correct current commands.
  • If the /landing/ redirect is a known dev quirk, I can document the workaround (e.g., use a clean port/host, clear service worker & site data).

Thanks in advance for the guidance! 🙏

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions