feat(types): make ImportMetaEnv strictly available

[yunics-highfield]

Description

Even if you want to make the type of ImportMetaEnv strict, you can't because [key: string]: any is specified. However, users should be able to choose whether to make the type strict or not.

/** vite-env.d.ts */

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

interface ImportMetaEnv {
  [key: string]: any // If you want to handle ImportMetaEnv ambiguously, add this by yourself.
  readonly MY_ENV: string;
{

[yunics-highfield]

I'll handle the lint error later.

[sapphi-red]

Would you add a document about this here?
https://vite.dev/guide/env-and-mode.html#intellisense-for-typescript

[yunics-highfield]

What do you think of this change?

• 43a8135

[sapphi-red]

In the last meeting, we decided to go with an interface instead of a simple type ViteStrictImportMetaEnv so that we can add options later on if needed. I pushed a commit for that.

[sapphi-red]

/ecosystem-ci run

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/vite@19077

commit: f0a3754

[vite-ecosystem-ci]

📝 Ran ecosystem CI on f0a3754: Open

suite	result	latest scheduled
histoire	❌ failure	✅ success
vite-plugin-svelte	❌ failure	❌ failure

✅ analogjs, react-router, previewjs, quasar, vite-plugin-pwa, vike, ladle, nuxt, qwik, laravel, waku, vite-plugin-react-swc, rakkas, vite-plugin-vue, vitepress, unocss, vite-setup-catalogue, vite-environment-examples, storybook, vite-plugin-react, sveltekit, vitest, vuepress, vite-plugin-cloudflare, marko, astro

[sapphi-red]

This PR only changes the types, so the failure of histoire is probably unrelated.