Mocking module react-router-dom returns undefined

[yukinami]

Describe the bug

Mocking module react-router-dom returns undefined after I set environment to jsdom.
If the environment is set to node. Everything works fine. And this only happens to react-router-dom, mocking other module also works fine.

Reproduction

import { renderHook } from '@testing-library/react';
import reactRouter from 'react-router-dom';
import { describe, expect, it, vi } from 'vitest';

import { useRouterAuthorize } from '../use-router-authorize';

vi.mock('react-router-dom');
describe('useRouterAuthorize', () => {
  it('should', async () => {
    const useMatches = vi.mocked(reactRouter.useMatches);  //reactRouter is undefined 
    useMatches.mockReturnValue([
      {
        id: '',
        pathname: '',
        params: {},
        data: null,
        handle: {
          access: ['admin'],
        },
      },
    ]);

    const { result } = renderHook(() => useRouterAuthorize(['admin']));
    expect(result.current).toBeTruthy();
  });
});

System Info

System:
    OS: macOS 12.0
    CPU: (8) arm64 Apple M1 Pro
    Memory: 91.52 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 18.9.1 - ~/.nvm/versions/node/v18.9.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.9.1/bin/yarn
    npm: 8.19.1 - ~/.nvm/versions/node/v18.9.1/bin/npm
  Browsers:
    Chrome: 108.0.5359.124
    Safari: 15.0
  npmPackages:
    @vitejs/plugin-react: ^2.1.0 => 2.2.0 
    vite: ^3.1.0 => 3.2.3 
    vitest: ^0.26.0 => 0.26.0

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.