You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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-access51:19 error Unsafe member access .DEV on an
any
value @typescript-eslint/no-unsafe-member-access146:9 error Unsafe member access .DEV on an
any
value @typescript-eslint/no-unsafe-member-accessDid 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
Used Package Manager
pnpm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: