> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemreference/functions/text/javascriptencode.md).

# JavascriptEncode

{% hint style="info" %}
The **`JavascriptEncode()`** function encodes the given value to a Javascript literal.

This function is NOT SQL compatible. For more information about SQL compatibility, see our [documentation](/platform/wemreference/sql-compatibility.md).
{% endhint %}

{% hint style="success" %}
Returns a <mark style="color:green;">text</mark> that contains a JavaScript literal.\
Returns <mark style="color:red;">`null`</mark> if the value is unknown.
{% endhint %}

### Syntax

<details>

<summary><code>JavascriptEncode(</code><mark style="color:blue;"><code>value</code></mark><code>)</code></summary>

`JavascriptEncode("\"Line 1\"\n'Line 2';")`\
\&#xNAN;*=> "\\"Line 1\\"\n\\'Line 2\\';"*

</details>

### Parameters

<table><thead><tr><th width="150">Name</th><th width="150">Type</th><th width="150" align="center">Required</th><th width="248.15953250810662">Description</th><th data-hidden>Required?</th></tr></thead><tbody><tr><td><mark style="color:blue;"><code>value</code></mark></td><td>any WEM value</td><td align="center"><span data-gb-custom-inline data-tag="emoji" data-code="2611">☑️</span></td><td>see hint below</td><td>yes</td></tr></tbody></table>

{% hint style="warning" %}
Value - any WEM value (strings, numbers, boolean, etc.). The following encoding is used for non-native JavaScript types:

* Concept - the concept ID is used
* Concept set - array of concept ID's is used
* Duration - the number of ticks (milliseconds) is used
* File - the URL as a string
* Reference - string representation of the referenced list and rowID
  {% endhint %}


---

# 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 dynamically by asking a question.

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

```
GET https://docs.wem.io/platform/wemreference/functions/text/javascriptencode.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.