SnapOtter 2927e0d4be fix(e2e): disable Astro Dev Toolbar during landing e2e tests ...

The Astro Dev Toolbar (enabled by default in dev mode) injects h1
elements ("No islands detected", "Audit", "Settings") and a
"Community" link inside its shadow DOM. Playwright CSS selectors
pierce shadow DOM, causing 6 test failures:

- 5 heading-hierarchy tests saw extra h1 elements from the toolbar
- footer "Community" column title resolved to 2 elements (footer h4
  plus toolbar's Astro community chat link)

Root-cause fix: set PLAYWRIGHT=1 env var in the Playwright webServer
command; Astro config conditionally disables devToolbar when set.
Normal development retains the toolbar.

2026-06-21 12:13:48 +08:00

..

public

feat(landing): generate 301 redirects for old tool URLs; fix robots sitemap reference

2026-06-20 23:56:03 +08:00

scripts

feat(landing): generate 301 redirects for old tool URLs; fix robots sitemap reference

2026-06-20 23:56:03 +08:00

src

fix(e2e,landing): robust path escaping (CodeQL) + unique file-tools card

2026-06-21 03:25:45 +08:00

.gitignore

feat(landing): migrate from Next.js to Astro 5

2026-06-14 16:50:20 +08:00

astro.config.mjs

fix(e2e): disable Astro Dev Toolbar during landing e2e tests

2026-06-21 12:13:48 +08:00

next-env.d.ts

feat: scaffold Next.js landing page app at apps/landing

2026-04-23 17:19:48 +08:00

package.json

feat(landing): generate 301 redirects for old tool URLs; fix robots sitemap reference

2026-06-20 23:56:03 +08:00

tsconfig.json

feat: scaffold Next.js landing page app at apps/landing

2026-04-23 17:19:48 +08:00

turbo.json

feat(landing): migrate from Next.js to Astro 5

2026-06-14 16:50:20 +08:00