Environment Variables
This documentation is for the preview version of the Dev Portal. If you are using the legacy developer portal, please refer to the docs.
Dev Portal is built on top of Vite and uses their approach for managing environment variables.
Dev Portal exposes environment variables under the import.meta.env
object as strings automatically.
To prevent accidentally leaking environment variables to the client, only variables prefixed with ZUDOKU_PUBLIC_
are exposed to your Zudoku-processed code.
Security Notice
Environment variables prefixed with ZUDOKU_PUBLIC_
will be exposed to the client-side code and visible in the browser. Never use this prefix for sensitive information like API keys, passwords, or other secrets.
Local Env Files
When developing locally, you can create a .env
file in the root of your project and add environment-specific variables. See the Vite documentation for more information on supported files.
Here is an example of a .env.local
file:
Code(sh)
You can access this variable in your application like this:
Code(ts)
Configuration Files
Environment variables can also be used in your configuration files. When referencing environment variables in your configuration files, you can use process.env
directly.
Code(ts)
React Components
If you need to access environment variables inside a custom react component, you can access them via import.meta.env
. Public environment variables are inlined during the build process.
Code(tsx)
IntelliSense for TypeScript
By default, Dev Portal provides type definitions for import.meta.env
in zudoku/client.d.ts
. While you can define more custom env variables in .env.[mode]
files, you may want to get TypeScript IntelliSense for user-defined env variables that are prefixed with ZUDOKU_PUBLIC_
.
To achieve this, you can create a zudoku-env.d.ts
in the src directory, then augment ImportMetaEnv
like this:
Code(typescript)
Imports will break type augmentation
If the ImportMetaEnv
augmentation does not work, make sure you do not have any import statements in vite-env.d.ts
. A helpful explanation can be found on this StackOverflow reply.