chore: type unknown env as any

[bluwy]

Description

Type import.meta.env.* as any for unknown keys, as the define option can be used to define import.meta.env.* too with JS identifiers.

Additional context

Brought up in #6930 and #4415 (comment)

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[sapphi-red]

How about adding this line? (in addition to this change)

Suggested change

	[key: string]: any
	[key: string]: any
	[env: `VITE_${string}`]: string

It requires template literal types support which is implemented in TypeScript 4.1+ (released 2020/11).

This type will work like below.

/// <reference types="vite/client" />

interface ImportMetaEnv {
  VITE_FOO: string
  VITE_BAR: 'aa' | 'bbb'
  VITE_AA: number // error "this should be string" here
}

import.meta.env.VITE_BAR // 'aaa' | 'bbb'
import.meta.env.VITE_VAL // string

One thing to consider is that you can't define variables that are not string types starting with VITE with define.

[bluwy]

One thing to consider is that you can't define variables that are not string types starting with VITE with define.

Yeah I think that's the issue from #6637 that people want to type it as boolean or number, but it was actually a string. And if they really want it to actually be a boolean/number, they have to use define for it. Not sure how common this is needed though, but your suggestion could be breaking some setups (though quite neat).

[patak-dev]

I think we should merge this PR in its current form for 2.9. And then, @sapphi-red maybe you could create another PR with your proposal and justify the Typescript version requirement, and we target 3.0 for the change?

[sapphi-red]

Sure. I will create a PR with more details.

[sapphi-red]

Oh there is a envPrefix option. It is impossible to do this approach.