> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/developer-guide/variables/client-side-variables/best-practices-to-follow-for-client-side-variables.md).

# Best Practices to Follow for Client-Side Variables

When working with **client-side variables** in JENTIS, it’s important to follow certain guidelines to ensure **maximum browser compatibility** and proper execution across all environments. Below are some helpful best practices to keep in mind:

***

#### Avoid Using `async` in Function Definitions

Functions for client-side variables **must not start with the `async` keyword**. Asynchronous logic is handled differently (e.g., via callbacks), and `async` is not supported in this context.

***

#### Stick to ES5 for Maximum Compatibility

To ensure your variable logic runs reliably across all browsers—including older ones—stick to **ES5 JavaScript syntax**.\
Check compatibility at [Can I use](https://caniuse.com/) if you're unsure whether a feature is supported.

***

#### Use `var` Instead of `let` or `const`

Always use `var` when declaring variables inside client-side variable functions. While `let` and `const` are common in modern JavaScript, they are **not fully supported in older browsers** that might still be in use.

***

#### Avoid `console.log()` for Debugging

Using `console.log()` inside a client-side variable can **disrupt execution** or lead to undesired behavior.\
Instead, use **JavaScript breakpoints** to inspect and debug your variable logic. You can place breakpoints directly in the **JENTIS JavaScript file** via the browser’s developer tools.

***

Following these simple practices will help you build **stable, compatible, and performant** client-side variables in JENTIS.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jentis.com/developer-guide/variables/client-side-variables/best-practices-to-follow-for-client-side-variables.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.