[🐞] vite incorectly processes import.meta.env in examples

[mhevery]

Which component is affected?

Qwik Runtime

Describe the bug

1. This line: https://github.com/BuilderIO/qwik/blob/main/packages/docs/src/routes/docs/labs/insights/index.mdx#L34
2. Generates:
   
   notice ({}) when it should be import.meta.env

Reproduction

https://qwik.builder.io/docs/labs/insights/

Steps to reproduce

Navigate to: https://qwik.builder.io/docs/labs/insights/
See:
notice ({}) when it should be import.meta.env

System Info

na

Additional Information

No response

[manucorporat]

it's almost like a vite / mdx issue

[TimKieu]

VITE: I also face this ENV with Vite React and Vite Hono/Express.
Vite cannot process import.meta.env or the older process.env

[gioboa]

🤔 that's because you need to call the env variables with the prefix VITE_

Extract from the documentation

To prevent accidentally leaking env variables to the client, only variables prefixed with VITE_ are exposed to your Vite-processed code. e.g. for the following env variables:

VITE_SOME_KEY=123
DB_PASSWORD=foobar
Only VITE_SOME_KEY will be exposed as import.meta.env.VITE_SOME_KEY to your client source code, but DB_PASSWORD will not.

console.log(import.meta.env.VITE_SOME_KEY) // 123
console.log(import.meta.env.DB_PASSWORD) // undefined

---

I think we can close this issue, @TimKieu is it solved for you?

[github-actions]

Hello @TimKieu . Please provide the missing information requested above.
Issues marked with STATUS-2: missing info will be automatically closed if they have no activity within 14 days.
Thanks 🙏