-
Notifications
You must be signed in to change notification settings - Fork 1k
Description
Both Getting Started guides fail on macOS (Quickstart + README)
Summary
Neither of the two official getting started paths work out of the box on macOS. As a new user trying A2UI for the first time, I was unable to get the demo running following either guide. This is likely a significant barrier for newcomers evaluating the project.
Environment
- OS: macOS (MacBook)
- Node.js: v18+
- Python: 3.13 (via conda env
py313) - uv: installed
- GEMINI_API_KEY: set
Issue 1: Quickstart guide — confusing directory navigation
Docs page: https://a2ui.org/quickstart/#step-4-install-and-run
Problem
The quickstart instructs users to navigate to samples/client/lit and run npm run demo:all. However, the repo also contains a renderers/lit directory, and it's easy to end up there instead — especially when browsing the repo structure or following the README's separate instructions which reference the renderers/ path.
Running npm run demo:all from renderers/lit produces:
npm error Missing script: "demo:all"
Issue 2: README Getting Started — multi-step manual build fails
Docs page: https://github.com/google/a2ui#getting-started
Problem
The README provides an alternative getting started flow that involves manually building multiple packages in sequence:
# Install and build the Markdown renderer
cd renderers/markdown/markdown-it
npm install
npm run build
# Install and build the Web Core library
cd ../../web_core
npm install
npm run build
# Install and build the Lit renderer
cd ../lit
npm install
npm run build
# Install and run the shell client
cd ../../samples/client/lit/shell
npm install
npm run devThis multi-step process fails on macOS. The number of sequential cd + npm install + npm run build steps makes it fragile — if any single step fails or produces an unexpected output, the entire chain breaks, and it's difficult for new users to diagnose which step went wrong.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status