mirror of
https://github.com/webstudio-is/webstudio.git
synced 2026-10-27 23:27:09 +09:00
Ivan Starkov
393cc90612
## Description This variables are build time and not dependent on deploy. Moreover we don't know them during production deploy. But they are used as versioning at saas level ## Steps for reproduction 1. click button 2. expect xyz ## Code Review - [ ] hi @kof, I need you to do - conceptual review (architecture, feature-correctness) - detailed review (read every line) - test it on preview ## Before requesting a review - [ ] made a self-review - [ ] added inline comments where things may be not obvious (the "why", not "what") ## Before merging - [ ] tested locally and on preview environment (preview dev login: 5de6) - [ ] updated [test cases](https://github.com/webstudio-is/webstudio/blob/main/apps/builder/docs/test-cases.md) document - [ ] added tests - [ ] if any new env variables are added, added them to `.env.example` and the `builder/env-check.js` if mandatory
13 lines
527 B
TypeScript
13 lines
527 B
TypeScript
/**
|
|
* Build-time Environment Variables
|
|
*
|
|
* These variables are injected into your bundle at build time based on the environment settings.
|
|
* - Configuration: See envPrefix in [vite.config.ts](../../vite.config.ts) (GITHUB_)
|
|
* - Documentation: Refer to the [Vite documentation](https://vitejs.dev/guide/env-and-mode)
|
|
* - Type Definitions: See [vite-env.d.ts](./vite-env.d.ts) in this directory
|
|
*/
|
|
export const staticEnv = {
|
|
GITHUB_REF_NAME: import.meta.env.GITHUB_REF_NAME,
|
|
GITHUB_SHA: import.meta.env.GITHUB_SHA,
|
|
};
|