Vue Typescript starter - import.meta.env unusuable

Hey currently you cannot use Vite’s enviroment variables with the Vue typescript starter because the the tsconfig module option is set to “CommonJS”.

tsconfig.json
{
  "compilerOptions": {
    "strict": true,
    "module": "CommonJS",
    "target": "ES2020",
    "lib": ["DOM"],
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "baseUrl": "./",
    "paths": {
      "~/*": ["./src/*"]
    },
  },
  "ts-node": {
    "transpileOnly": true
  }
}

Is there a way around this?

[brillout]

Hm, seems like a bug in ts-node. But yea you’ll eventually find the problem by further digging 😃

On Mon, Jul 19, 2021 at 2:32 PM Stephen Samra @.***> wrote:

@brillout https://github.com/brillout, you were right that ts-node was not picking up the tsconfig.json#ts-node options.

Adding a console.log inside ts-node for those options showed:

{ “transpileOnly”: undefined, “compilerOptions”: undefined}

However, when I inline those options in the package.json script like so:

“scripts”: { “dev”: “ts-node --transpile-only --compiler-options ‘{"module":"CommonJS"}’ ./server”, }

… it shows:

{ “transpileOnly”: true, “compilerOptions”: { “module”: “CommonJS” }}

Unfortunately, even with those options set, I still get the same error so I’m still looking into it. Thanks for the help thus far though!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/brillout/vite-plugin-ssr/issues/101#issuecomment-882509794, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHVQRWCCFFMUWFQJD7NTOLTYQLNVANCNFSM463XKSXQ .

[brillout]

@deckchairlabs That is correct. In particular import.meta doesn’t exist in server.js. But better to have false positive than not being able to use import.meta at all.