vite 2.4.0: importMeta.d.ts types not exporting ImportMeta and ImportMetaEnv

[userquin]

Describe the bug

Typescript cannot resolve import.meta.globEager:

Reproduction

not required, just see importMeta.d.ts file

System Info

System:
    OS: Windows 10 10.0.19042
    CPU: (16) x64 Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
    Memory: 46.12 GB / 63.95 GB
  Binaries:
    Node: 15.11.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - C:\Program Files\nodejs\yarn.CMD
    npm: 7.6.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 91.0.4472.124
    Edge: Spartan (44.19041.1023.0), Chromium (91.0.864.64)
    Internet Explorer: 11.0.19041.1
  npmPackages:
    @vitejs/plugin-vue: ^1.2.4 => 1.2.4
    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.

[IanVS]

globEager is defined at https://github.com/vitejs/vite/blob/main/packages/vite/types/importMeta.d.ts#L54. Was this working for you in a previous version of vite, and broke in an upgrade? Have you added the vite client types as shown in https://vitejs.dev/guide/features.html#client-types?

[userquin]

Yes, migrated from 2.3.8 or 2.3.7 and updated vía taze, I'll try tmr, thx.

[userquin]

Why are not exported on d.ts file? I'm missing something?? Maybe New ts version??

[userquin]

I'm testing with vitesse template and have the second approach of the doc using types on tsconfig.json file:

https://github.com/antfu/vitesse/blob/master/tsconfig.json#L17

[userquin]

It is not a problem since build is working, but my intellij ide not resolving this type, while using prevoius versión, the entry on tsconfig.json file just resolves the type.

[IanVS]

Why are not exported on d.ts file?

It is a property that is being defined on the ImportMeta interface, which is what typescript assigns to import.meta.

I believe this is probably the same problem as #4125, and I think the PR I have opened will solve your issue too.

[avocadowastaken]

Edit: #4134 (comment)

---

I fixed it by importing everything manually.

- /// <reference types="vite/client" />
+ import 'vite/client';
+ import 'vite/types/importMeta';

+ declare module 'vite/client' {
  interface ImportMetaEnv {
    LEGACY: boolean;
  }
+ }

[patak-dev]

Thanks @umidbekk, could you check that #4138 fixes the issue for you? You can check the history of PRs there, looks like import would fail in other cases so triple dashes were introduced

[avocadowastaken]

@patak-js This actually fixed the problem!

So better workaround is:

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

  interface ImportMetaEnv {
    LEGACY: boolean;
  }

[patak-dev]

@umidbekk we also tried that, check #4031 to see what was the problem with this one. We just merged #4138 which seems to work across the board, it would be good to check main, as we will release this as 2.4.1 soon

[userquin]

cloning main repo working

[patak-dev]

Closed in #4138