Files
SnapOtter/apps/landing/astro.config.mjs
T
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

27 lines
568 B
JavaScript

import sitemap from "@astrojs/sitemap";
import tailwindcss from "@tailwindcss/vite";
import { defineConfig } from "astro/config";
export default defineConfig({
site: "https://snapotter.com",
output: "static",
devToolbar: {
enabled: !process.env.PLAYWRIGHT,
},
integrations: [
sitemap({
filter: (page) => !page.includes("/404"),
}),
],
vite: {
plugins: [tailwindcss()],
resolve: {
extensions: [".ts", ".tsx", ".js", ".jsx"],
conditions: ["import", "module"],
},
},
build: {
format: "directory",
},
});