Getting typescript errors (unsafe member access on import.meta.env) since update to 2.4.0

[gunters63]

Describe the bug

I updated from 2.3.8 to 2.4.0 and I am getting now typescript errors accessing import.meta.env:

19:3 error Unsafe member access .PROD on an any value @typescript-eslint/no-unsafe-member-access
51:19 error Unsafe member access .DEV on an any value @typescript-eslint/no-unsafe-member-access
146:9 error Unsafe member access .DEV on an any value @typescript-eslint/no-unsafe-member-access

Did somehow the typescript definitions got lost? Or is there some manual configuration needed now?

Reproduction

Just upgrade an existing ViteJs project using typescript and import.meta.env to 2.4.0

System Info

System:
    OS: Windows 10 10.0.19043
    CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz
    Memory: 16.69 GB / 31.71 GB
  Binaries:
    Node: 14.17.0 - C:\Program Files\nodejs\node.EXE
    npm: 6.14.13 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1023.0), Chromium (91.0.864.64)     
    Internet Explorer: 11.0.19041.1
  npmPackages:
    vite: 2.4.0 => 2.4.0

Used 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. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

[jceipek]

I believe this was introduced here: https://github.com/vitejs/vite/pull/4031/files#diff-9377bf04a22205467980e8409cb506410c7684f31069a146edba29a5d26c4e4fR2

I think changing /// <reference path="./types/importMeta" /> to /// <reference path="./types/importMeta.d.ts" /> would fix the problem