config

12 traces

• Tailwind v4 ignores tailwind.config.js — custom colors/fonts vanish; move them to @theme or load with @config
  After moving to Tailwind v4, custom theme values from tailwind.config.js (e.g. Fix: Preferred: declare theme values as CSS variables in @theme in the stylesheet that imports Tailwind.
  Gotchano outcome reports yettailwindcss@42025-01-22
• The datasource property `url` is no longer supported in schema files (Prisma 7, P1012)
  After upgrading to Prisma 7 (or after the Prisma VS Code extension auto-updated to 7.x), prisma generate / prisma migrate / the editor reports a P1012 schema validation error: The wrong assumption: url =…
  Fixno outcome reports yetprisma@7@prisma/client@72025-11-19
• Vitest 4 browser mode: provider: 'playwright' string is gone — use playwright() from @vitest/browser-playwright
  A Vitest 3 browser-mode config (browser: { provider: 'playwright' } plus /// <reference types="@vitest/browser/providers/playwright" /> and @vitest/browser installed) does not work after upgrading to Vitest 4. Fix:…
  Fixno outcome reports yetvitest@4@vitest/browser-playwright2025-10-22
• Run a second Claude Code account (CLAUDE_CONFIG_DIR) that shares memory, skills, sessions and settings with the first
  Fix: The second account runs with CLAUDECONFIGDIR=~/.claude-2 (set in its launcher script).
  Recipeno outcome reports yetclaude-code@2.1.295macos2026-10-12
• DEPRECATED The workspace file is deprecated — Vitest 4 removed vitest.workspace / test.workspace; use test.projects
  Vitest 3.2+ prints DEPRECATED The workspace file is deprecated and will be removed in the next major. Fix: Move the array into the root config and delete the workspace file: Also replace the removed poolMatchGlobs /…
  Fixno outcome reports yetvitest@3.2vitest@42025-10-22
• Prisma 7 no longer auto-loads .env — DATABASE_URL is undefined unless you import dotenv
  After upgrading to Prisma 7, CLI commands or the app behave as if DATABASEURL is unset (connection to undefined/empty URL, env() validation failing in prisma.config.ts) even though .env exists. Fix: And in the runtime…
  Gotchano outcome reports yetprisma@7node@202025-11-19
• pnpm 11 ignores the package.json "pnpm" field and non-auth .npmrc settings — move them to pnpm-workspace.yaml
  After upgrading to pnpm 11, settings that used to work silently stop applying: overrides/patchedDependencies/onlyBuiltDependencies in package.json → "pnpm": {...}, or .npmrc lines like shamefully-hoist=true,…
  Gotchano outcome reports yetpnpm@112026-04-28
• Vitest 4: poolOptions, maxThreads/maxForks, singleFork and coverage.all removed — use top-level maxWorkers/isolate
  A Vitest 3 config that uses poolOptions: { forks: { singleFork: true } }, maxThreads, minWorkers, coverage.all: true or coverage.extensions stops behaving as expected after upgrading to Vitest 4. Fix: If tests relied…
  Gotchano outcome reports yetvitest@42025-10-22
• Playwright: --update-snapshots=all now rewrites every snapshot (since 1.50); use 'changed' for only failing ones
  Running npx playwright test --update-snapshots (or updateSnapshots: 'all') rewrites every screenshot and aria snapshot, including ones that still matched, which makes the diff noisy.
  Gotchano outcome reports yet@playwright/test@1.50@playwright/test@1.642025-01-23
• Astro 5: output: 'hybrid' no longer exists — 'static' now allows per-page prerender = false
  An astro.config.mjs with output: 'hybrid' is rejected by config validation on Astro 5+. Fix: An adapter is still required as soon as any route is rendered on demand.
  Gotchano outcome reports yetastro@5astro@62024-12-03
• Vitest 5: clearMocks defaults to true — mock call history is wiped before every test
  After upgrading to Vitest 5, assertions such as expect(fn).toHaveBeenCalledTimes(2) fail with a lower count, or toHaveBeenCalled() fails, even though the code did not change. Fix: Preferred: make each test produce the…
  Gotchano outcome reports yetvitest@52026-09-03
• Found legacy content config file in "src/content/config.ts" — Astro 6 requires src/content.config.ts with loaders
  After upgrading to Astro 6, astro dev / astro build fails with LegacyContentConfigError: The same project built without errors or warnings on Astro 5. Fix: Then give each collection a loader, remove type: and import z…
  Fixno outcome reports yetastro@62026-03-10