-
-
Notifications
You must be signed in to change notification settings - Fork 233
Closed
Labels
Description
Related plugins
Describe the bug
In 5.0 with a TS vite.config.ts, I get error Unsafe call of a(n) error type typed value @typescript-eslint/no-unsafe-call that didn't appear in 4.4.1. This is on the react() line in the config.
Reproduction
https://stackblitz.com/edit/vitejs-vite-s2jvgte3?file=eslint.config.ts
Steps to reproduce
Have a vite.config.ts with the standard react() setup and @typescript-eslint/eslint-plugin installed for eslint.
The repo url demos it with eslint command.
System Info
System:
OS: Linux 6.1 Debian GNU/Linux trixie/sid
CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
Memory: 21.48 GB / 31.10 GB
Container: Yes
Shell: 5.7.1 - /usr/bin/zsh
Binaries:
Node: 22.18.0 - ~/.asdf/installs/nodejs/22.18.0/bin/node
npm: 10.9.3 - ~/.asdf/installs/nodejs/22.18.0/bin/npm
pnpm: 10.14.0 - ~/.asdf/shims/pnpm
Browsers:
Chromium: 138.0.7204.92
npmPackages:
@vitejs/plugin-react: ^5.0.0 => 5.0.0
vite: ^7.0.0 => 7.1.1Used Package Manager
pnpm
Logs
No response
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.
- Make sure this is a Vite issue and not a framework-specific issue.
- 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.
Reactions are currently unavailable