[next-lint] test: remove eslint config snapshot testing

[devjiwonchoi]

Why?

The snapshot testing occasionally failed when the rules were modified in newer ESLint versions. This is because we snapshot-tested the whole eslint config output. However, this snapshot test is intended to verify if the necessary plugins were loaded, which can be done by checking the plugins property.

How?

Removed snapshot testing and added plugins to be checked along with the existing parser and settings checking.

[devjiwonchoi]

• [next-lint] test: remove eslint config snapshot testing #77818 👈 (View in Graphite)
• canary

This stack of pull requests is managed by Graphite. Learn more about stacking.

[ijjk]

Failing test suites

Commit: bfdbb66

pnpm test-dev test/e2e/app-dir/rsc-basic/rsc-basic.test.ts

• app dir - rsc basics > should be able to navigate between rsc routes

Expand output

● app dir - rsc basics › should be able to navigate between rsc routes

request.allHeaders: Target page, context or browser has been closed

  168 |         page.on('request', (request) => {
  169 |           requestsCount++
> 170 |           return request.allHeaders().then((headers) => {
      |                          ^
  171 |             if (
  172 |               headers['RSC'.toLowerCase()] === '1' &&
  173 |               // Prefetches also include `RSC`

  at Page.allHeaders (e2e/app-dir/rsc-basic/rsc-basic.test.ts:170:26)

Read more about building and testing Next.js in contributing.md.

[eps1lon]

However, this snapshot test is intended to verify if the necessary plugins were loaded, which can be done by checking the plugins property.

That was not the intention. The intention is to check the full config so see if a bump to plugins counts as a breaking change. This should be reverted and reconsidered. What specifically in the config changes?