src/environments/vitest/env/jsdom.ts (1)

7-7: Add error handling for missing jsdom optional peer dependency to match the existing pattern used for other optional peers (like playwright-core in src/e2e/browser.ts).

At Line 7, wrap the import in a try-catch block and throw a descriptive error with installation guidance if the module is not found:

Proposed patch

-  const { CookieJar, JSDOM, ResourceLoader, VirtualConsole } = await import('jsdom')
+  let jsdomModule: typeof import('jsdom')
+  try {
+    jsdomModule = await import('jsdom')
+  }
+  catch (error) {
+    throw new Error(
+      'Missing optional peer dependency "jsdom". Install it in your project (e.g. `pnpm add -D jsdom`).',
+      { cause: error as Error },
+    )
+  }
+  const { CookieJar, JSDOM, ResourceLoader, VirtualConsole } = jsdomModule

Note: src/environments/vitest/env/happy-dom.ts has the same issue and should receive the same treatment.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/environments/vitest/env/jsdom.ts` at line 7, Wrap the dynamic import of
jsdom in a try-catch so missing optional peer dependency is handled: replace the
direct await import('jsdom') that destructures CookieJar, JSDOM, ResourceLoader,
VirtualConsole with a try block and in catch throw a descriptive Error advising
to install jsdom (e.g. "jsdom is required for this environment — install with
`npm i -D jsdom`"), preserving original variable names (CookieJar, JSDOM,
ResourceLoader, VirtualConsole) for use after the import; apply the identical
try-catch pattern to the similar import in the happy-dom environment file as
well.

pnpm-workspace.yaml (1)

22-22: Document the rationale for ignoreWorkspaceRootCheck: true to prevent accidental root-level dependency drift.

At Line 22, disabling this guard allows pnpm add ... to modify the workspace root package.json without the explicit -w/--workspace-root flag. While this reduces friction if root-level tooling dependencies are intentional, it increases the risk of silently accumulating dependencies that should be scoped to specific packages, weakening workspace boundaries. Add a comment in pnpm-workspace.yaml or update contributing docs to clarify why this is disabled.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@pnpm-workspace.yaml` at line 22, Add a short rationale near the existing
setting by commenting why ignoreWorkspaceRootCheck: true is enabled: state that
it permits intentional root-level tooling installs (e.g., CI/tools) and that
contributors should prefer package-scoped dependencies unless adding global
workspace tools; also reference the contributing docs where you describe the
policy and the required use of -w/--workspace-root when adding root deps. Update
the pnpm-workspace.yaml to include this explanatory comment adjacent to
ignoreWorkspaceRootCheck: true and add or update the contributing guide section
on workspace root dependency policy to prevent accidental root-level dependency
drift.