Import.meta error in vite 3.1.3

[chesterlaykin]

Describe the bug

There appears to be a bug in vite 3.1.3: when using vite with react and typescript (using a package called vite-plugin-ssr) I get errors beginning with:
[vite] warning: "import.meta" is not available in the configured target environment ("ES2017") and will be empty

If I change the version to vite 3.0.9, the error goes away.
The issue is with the vite version rather than the vite-plugin-ssr package, as I understood it.
Here is a reproduction: .

tsconfig has"module": "ES2020"and:

"ts-node": {
    "transpileOnly": true,
    "compilerOptions": {
      "module": "CommonJS"
    }
  }

Reproduction

https://stackblitz.com/edit/github-c4bkhn

System Info

System:
    OS: Windows 10 10.0.19044
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 3.16 GB / 15.73 GB
  Binaries:
    Node: 16.16.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 8.11.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (105.0.1343.42)
    Internet Explorer: 11.0.19041.1566

Used Package Manager

yarn

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 vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[OliverGrimsley]

Similar issue in vue plugin - I can confirm - if I set version to 3.0.9, my app builds in production and development, HMR works, etc no issues. If I move the Vite dependency to 3.1.0, I have the problem noted in this discussion thread - but to reduce it down, something in the new code in 3.1.1 started injecting import_meta (and please note the underscore) as a blank object, and then trying to read from it. If I view the same compiled code in development under v 3.0.9, there is no reference to import_meta and the later call is to import.meta - I think these are related issues is why I posted here and did not open a new issue.

[htmnk]

#10167 might be related, similiar import.meta issues went away for me after setting esbuild.target to 'esnext' as a workaround.

[OliverGrimsley]

I can confirm changing target to esnext in TS compile options fixed issue for me. thx!

[chesterlaykin]

That works for me too, great!

[sapphi-red]

Yeah, it's happening by the same cause with #10167.
Closing to keep the discussion in a single place.