> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

# Method name: env()

# Method package: wixRouter

# Method menu location: wixRouter --> WixRouterRequest --> env

# Method Link: https://dev.wix.com/docs/velo/events-service-plugins/routers/service-plugins/wix-router/wix-router-request/env.md

# Method Description:

Returns the current environment the router rendering process is running in.

When possible, the rendering process is split in two in order to
 improve performance. The first cycle in the process is initiated from backend rendering,
 and the second cycle is initiated from client-side rendering. Note that
 even when the rendering cycle is initiated from client-side rendering, router code is called, 
 and router code always runs in the backend.
 
 If not possible on the backend, all rendering
 is initiated from the client side.

 The `env` property returns `"backend"` when rendering on the backend,
 and `"browser"` when rendering on the client.

 Use the `env` property in your page's [`onReady()`]($w.html#onReady)
 event handler to control where your code runs during the rendering
 process and to prevent code that causes side effects from running twice.

 > **Note:** Rendering never occurs on the backend when previewing your site.



# Method Code Examples:

*** Note: do not assume any prop names or enum values other than the ones in the example.

## Get the current environment the router request is running in

```javascript
export function myRouter_Router(request) {

  let env = request.env; // "backend"

}
```

---