no-node-access rule incorrectly triggering from RTK Query syntax in 7.5.4

[MrZipper7]

Have you read the Troubleshooting section?

Yes

Plugin version

7.5.4

ESLint version

v9.30.1

Node.js version

20.19.3

Bug description

After updating to 7.5.4, all instances of RTK Query's endpoint.select() method (https://redux-toolkit.js.org/rtk-query/api/created-api/endpoints#select) are triggering no-node-access errors.

Ex:

const data = api.endpoints.getAllPosts.select(undefined)(store.getState()).data?.data
                                       ~~~~~~
expect(data).toEqual(expectedData)

Steps to reproduce

1. Define an RTK Query endpoint (https://redux-toolkit.js.org/rtk-query/api/createApi#createapi-parameters.
2. Call the select function of the endpoint in a test.
3. Observe the no-node-access error.

Error output/screenshots

ESLint configuration

  {
    files: ['src/**/__test__/*', 'src/**/*.test.ts', 'src/**/*.test.tsx'],
    extends: [
      testingLibrary.configs['flat/react'], 
      vitest.configs.recommended
    ],
    rules: {
      'testing-library/render-result-naming-convention': 'off',
    }
  },

Rule(s) affected

no-node-access

Anything else?

No response

Do you want to submit a pull request to fix this bug?

No

[WikiRik]

I'm experiencing a similar issue I think. I'm accidentally running these rules on non-test files as well and I get a lint error on the following piece of code;

    const anchor = document.createElement("a");
    anchor.href = "/api/download?fileName=test.csv";
    anchor.click();

[spennine]

similar issue in our codebase: element.click() is triggering the lint error for us as well

none of the files cited as violating the rule in our codebase are tests, they're all runtime code

                        const element = document.getElementById(id);
                        if (element && !checked) {
                          element.click();
                        }

[Belco90]

For those having issues in your codebase: you should run this plugin only against test files.

[MrZipper7]

@Belco90 For clarification, at least in my case, this is happening in test files.

[lordlpua]

We also have some problems with the new rules. https://testing-library.com/docs/react-testing-library/setup - We have a utils file, similar to this example.
import { renderWithProviders, screen, userEvent } from '@testutils';
Or if renderWithProviders returns userEvent, ESLint will show an error. - ESLint: Avoid direct Node access. Prefer using the methods from Testing Library. (testing-library/no-node-access)
But initially, userEvent is an export directly from testing-library. Only in test files, of course.

[MrZipper7]

By way of further distinguishing from #1038, the files experiencing this issue are all unit tests that don't import from testing-library (or a custom export of testing-library utils) at all, and as far as I can tell, T-L doesn't appear anywhere up the import tree for them.

That makes me think that #1042 still might actually be useful here, but I'll be curious to see if #1043 ends up fixing it anyway as a side effect.