# Env

Statically defined environment variables enable a script to define configuration that's accessible from `scrip.env` based on weights and environment. `env` vars appear as properties of `script.env`.

Values can be any static literal, including object and arrays.

Note: env variables cannot override any built-in script.env variables such as version, url, etc.

### @env(options)

*Arguments*

* `options` { Object } Optional options object.
  * `name` { String } Optional name to override declared member name.
  * `environment` { String = *"\*"* } production, development, \*
  * `weight` { Number = *0* }
  * `active` { Boolean = *true* } Enable or disable entirely.

## Examples

```javascript
const { env } = require('decorators')      

class EnvVars {

  @env({name: 'myEnv__foo',  environment: 'development' })
  static devFoo = 'dev bar'

  @env({name: 'myEnv__foo',  environment: 'production' })
  static prodFoo = 'prod bar'

  @env
  static myobj = {
    foo: 'bar',
    arr: [1, 2, 3]
  }

}

// --------------

return script.env

// {  
//   "myEnv__foo": "dev bar",
//   "myobj": {
//     "arr": [
//       1,
//       2,
//       3
//     ],
//     "foo": "bar"
//   },
//   "name": "development",
//   // ...
// }
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.medable.com/cortex-api/decorators/static/env.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.