[vite-typescript] how to use 'import.meta'

[w3cways]

Pre-flight checklist

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project uses.
• I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version

6.4.1

Electron version

26.0.0

Operating system

macOS 12.4

Last known working Electron Forge version

none

Expected behavior

when I use 'import.meta' in renderer.ts, prompt error :'The "import.meta" meta property is only allowed when the "--module" option is "es2020", "es2022", "esnext", "system", "node16", or "nodenext"'

tsconfig.json
{ "compilerOptions": { "target": "ESNext", "module": "commonjs", "allowJs": true, "skipLibCheck": true, "esModuleInterop": true, "noImplicitAny": true, "sourceMap": true, "baseUrl": ".", "outDir": "dist", "moduleResolution": "node", "resolveJsonModule": true }, "include": ["src"] }
if I change 'commonjs' to 'ESNext', then run command 'npm run start', got errors:
An unhandled rejection has occurred inside Forge: SyntaxError: Cannot use import statement outside a module

Is there a way to fix this?

Actual behavior

can use 'import.meta' in [vite-typescript]

Steps to reproduce

   use 'import.meta' in renderer.ts

Additional information

No response

[caoxiemeihao]

You can try this!

{
  "compilerOptions": {
-   "module": "commonjs",
+   "module": "ESNext",
  }
}

🤔 However this seems to conflict here 👉 #3178 (comment)

[yang131323]

You can try this!

{
  "compilerOptions": {
-   "module": "commonjs",
+   "module": "ESNext",
  }
}

🤔 However this seems to conflict here 👉 #3178 (comment)

Then when compiling with vite,i cannot use 'import.meta'.Is that so?

[wutiange]

@w3cways How did you finally solve this problem?

[w3cways]

@w3cways How did you finally solve this problem?

{
"ts-node": {
// these options are overrides used only by ts-node
// same as our --compilerOptions flag and our TS_NODE_COMPILER_OPTIONS environment variable
"compilerOptions": {
"module": "commonjs"
}
},
"compilerOptions": {
"target": "esnext",
"module": "esnext",
"lib": ["dom", "dom.iterable", "esnext"],
"isolatedModules": true,
"allowJs": true,
"skipLibCheck": true,
"esModuleInterop": true,
"noImplicitAny": true,
"sourceMap": true,
"baseUrl": ".",
"outDir": "dist",
"moduleResolution": "Node",
"resolveJsonModule": true,
"typeRoots": ["./types"],
"types": ["vite/client", "@types/node"]
},
"include": ["src/*", "./types"],
"exclude": ["node_modules"]
}

[jamesopti]

What is the expected way to do this now?

I followed the setup using npm init electron-app@latest my-app -- --template=vite-typescript and still am unable to use import.meta

EDIT: I had left formats: ['es'], in the config.build.lib setting when debugging.

Removing it and going with @w3cways solution worked