test: clarify dev-only intent of duplicate Sass warning test (#98917)
## Summary Clarify that the duplicate Sass dependency warning test belongs in dev-mode coverage. The warning is emitted by `next dev`, which the test explicitly launches, but the test was previously scheduled only in production/start-mode jobs. Use a suite-level `@force-gate dev` in place of the start-mode guards and deployment skip. This is a test-organization cleanup: the previous arrangement could exercise the warning correctly, and this change adds no coverage or Next.js behavior changes. Fixture preparation, warning assertions, and process cleanup remain unchanged. ## Verification - Formatting, ESLint, and whitespace checks passed. - Focused Jest collection confirmed the scope is skipped in start and deploy modes. - Dev runtime verification and bootstrap build remain unverified: local pnpm commands stalled before producing output, including `pnpm --version`. Direct Jest collection also reported an existing SWC/package version mismatch. CI must validate the dev-mode execution. <!-- NEXT_JS_LLM -->
Showing
Please
register
or
sign in
to comment