fix(ci): silence TS5101 baseUrl deprecation for Playwright builds

[BigSimmo]

Summary

• Next 16.3 (landed via chore(deps): bump the npm-production group with 5 updates #1793) typechecks the isolated .next-playwright/*/tsconfig.json during production UI / Lighthouse builds.
• That generated config sets baseUrl so @/* still resolves from the repo root; TypeScript 6 reports TS5101 and fails Production UI critical.
• Add ignoreDeprecations: "6.0" to the Playwright and Lighthouse generated tsconfigs and to root tsconfig.json.

Test plan

• tsc -p against a generated playwright-style tsconfig with ignoreDeprecations succeeds locally
• CI Production UI critical / related build path green on this tip
• Unblocks open PRs that synced main after chore(deps): bump the npm-production group with 5 updates #1793 and are failing the same TS5101 gate

Risk

Low: silences a known TypeScript 6 deprecation for an intentional temporary baseUrl in isolated build roots. No product behaviour change.

RAG impact: no retrieval behaviour change — CI/tsconfig only.

  

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 8 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c8651936-ce96-49cf-8054-063ccca9ca14

📥 Commits

Reviewing files that changed from the base of the PR and between c163f3e and 0c041c6.

📒 Files selected for processing (3)

• scripts/run-lighthouse-budget.mjs
• scripts/run-playwright.mjs
• tsconfig.json

---

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Babysit summary (merged)

• Tip at merge: 0c041c6aeab69aa315907ead275734ea250936c6
• Sync/merge-tree: clean vs main
• Blocked by: Next 16.3 + TS6 TS5101 on Playwright/Lighthouse isolated baseUrl tsconfigs (broke Production UI critical after chore(deps): bump the npm-production group with 5 updates #1793)
• Fixed: ignoreDeprecations: "6.0" in generated Playwright/Lighthouse tsconfigs and root tsconfig.json
• Required CI: green; squash-merged as ee4e4789328f476068e8b35d59e5d9c853d94ed5
• Residual risks: temporary silence until @/* paths migrate off baseUrl
• Merge: completed — unblocks UI-gated open PRs