// Use when running Playwright tests in this repo (luna.mbt) and either the test fails to discover specs ("did not expect test.describe()" / "two different versions of @playwright/test") or you're adding a new playwright config under astra/ or sol/. Captures the version-skew between root and per-package @playwright/test pins.
Use when running `sol new` for the first time, when `sol <subcommand>` fails with `failed to resolve path mizchi/sol/cmd/sol_js` / `Run this command inside a MoonBit project that depends on mizchi/sol.`, or when moving from `sol dev` to `sol build` / `sol serve` for the first time. Covers (a) the bootstrap rules — `sol new <name> --user <ns>` works in an empty directory as of sol 0.22.2, but `--cloudflare` / `--doc` / `--dev` still need a host moon project, and every non-new subcommand needs `.mooncakes/mizchi/sol/` locally (= `moon install` after `sol new`) — (b) the sol 0.22.x scaffold layout (`app/server/routes.mbt` holds routes + page handlers; `app/layout/` is a separate package; `/` and `/about` are pre-registered) and (c) the production flow gotchas (`sol build` writes to two directories, `sol serve` does NOT rebuild, dev & prod both default to :7777).
Page description for <meta>
Use whenever working with `mizchi/luna` in the luna.mbt repo — writing CSR examples, fixing reactivity bugs (effects re-running on unrelated signal changes), adding new luna features, or onboarding to luna's mental model. This is the unified entry point; pick the right reference page below for the specific situation.
Use when deploying sol_app (or any sol-built MoonBit SSR worker) to Cloudflare Workers, debugging error 10021, or extending sol/examples/sol_app/scripts/patch-cloudflare-globals.mjs. Captures the global-scope I/O traps in MoonBit core + sol's generated bundle and the wrangler ASSETS binding URL layout.
| name | playwright-pnpm-workspace |
| description | Use when running Playwright tests in this repo (luna.mbt) and either the test fails to discover specs ("did not expect test.describe()" / "two different versions of @playwright/test") or you're adding a new playwright config under astra/ or sol/. Captures the version-skew between root and per-package @playwright/test pins. |
luna.mbt root pins @playwright/test@^1.58.2, but astra/package.json and sol/package.json independently pin ^1.59.1. Running pnpm exec playwright from the repo root resolves the older root-level version, while spec files imported from astra/e2e/ or sol/e2e/ resolve the newer per-package one. Playwright crashes with "did not expect test.describe()" because the registered test type and the discovered file disagree on which copy of @playwright/test they're holding.
This skill records which command to use for which directory and avoids burning a CI cycle on a version-skew bug.
astra/e2e/ or sol/e2e/Playwright Test did not expect test.describe() to be called here at test discovery@playwright/test versions across the monorepojust test-… recipe that drives playwright| Specs in | Use this command | Why |
|---|---|---|
luna/e2e/** | pnpm exec playwright … (from repo root) | luna/ is not a separate workspace package; tests resolve through root's @playwright/test@1.58.2. |
astra/e2e/** | cd astra && pnpm exec playwright … or pnpm -F @mizchi/astra-e2e exec playwright … | astra/package.json pins 1.59.1; root's 1.58.2 will crash. |
sol/e2e/** | pnpm -F @luna_ui/sol-workspace exec playwright … | sol/package.json pins 1.59.1 too. cd sol is unreliable here because zsh redirects sol to a sibling repo via hash -d. |
Wired examples in justfile:
test-deployed-luna:
pnpm playwright test --config luna/e2e/deployed/playwright.config.mts
test-deployed-website:
cd astra && pnpm exec playwright test --config e2e/deployed/playwright.config.mts
test-sol-chaos:
pnpm -F @luna_ui/sol-workspace exec playwright test --config "$(pwd)/sol/e2e/playwright-sol-app-chaos.config.mts"
The $(pwd)/... absolute path on test-sol-chaos is intentional — pnpm -F runs in the workspace's own cwd, so a relative config path would resolve wrong.
@playwright/test version applies.testDir, add the new path to the existing config's testIgnore so the original suite doesn't accidentally pick it up.just test-… recipe matching the runner table above.Playwright Test did not expect test.describe() to be called here — you're running with the wrong @playwright/test for the test file.Error: No tests found after the above — same root cause; playwright bailed before discovery completed.astra/e2e/deployed/ passes locally but the luna-e2e CI job fails referencing the same file — the localhost playwright config is also picking up the deployed/ specs because of glob-greedy testMatch. Add testIgnore: ["**/deployed/**"].cd sol in zsh on this machine redirects to ~/ghq/github.com/mizchi/sol.mbt (a sibling repo), not luna.mbt/sol/. Use pnpm -F instead, or absolute paths.testMatch is rooted at testDir but ** globs cross subdirectories. A new sibling dir under an existing testDir will be picked up unless explicitly ignored.vitest-browser (root devDep) currently pulls in @vitest/browser-playwright@4.0.18 which has its own playwright peer constraint. Check the unmet-peer warnings before dragging the root version forward.pnpm -F runs in the package's cwd. Relative --config paths won't resolve as you expect when the package is nested. Pass an absolute path ($(pwd)/sol/e2e/...) or cd into the package first.luna/e2e/playwright.config.mts, astra/e2e/playwright.config.mts, sol/e2e/playwright.config.mts — the three roots; each ignores **/deployed/** (and luna's also ignores **/visual-snapshots.test.ts in CI).justfile — the canonical recipes.