# Globals

The scene runtime ensures the existence of certain objects and functions inside the sandboxed Javascript environment, in addition to the standard utilities such as `Promise`, `Date` or `Math`.

{% hint style="info" %}
The globals described below are typical JavaScript concepts, but they are tailored to the Decentrland scene runtime and may not behave identically to their counterparts in browser or Node environments.
{% endhint %}

### Globals

The runtime injects 6 definitions in the scene's global scope:

1. [`console`](#console): a simplified version of the typical `console` object.
2. [`exports`](#module): an object where the scene can add its [public interface](https://github.com/decentraland/docs/blob/main/contributor/execution.md).
3. [`module`](#module): a container for the `exports` object.
4. [`require`](#module): a function to load runtime-provided modules by name.
5. [`fetch`](#http): a restricted implementation of the browser `fetch` function.
6. [`WebSocket`](#http): a restricted implementation of the browser `WebSocket` class.

All of these are defined as read-only properties, so they cannot be reassigned. Some will throw exceptions when used unless certain [permissions](https://github.com/decentraland/docs/blob/main/contributor/contributor/content/entity-types/scenes.md#permissions) are granted to the scene.

### Console <a href="#console" id="console"></a>

Scenes have access to a `console` object, much like the one provided by a browser or Node environment, though limited to only some of the methods you would normally find.

```ts
type Console = {
  log(...args: any): void
  info(...args: any): void
  debug(...args: any): void
  warning(...args: any): void
  error(...args: any): void
}
```

Just like their standard counterparts, each method takes variable arguments of any type and renders them as human-readable messages. For example, this is valid:

```js
console.log("The thing just appeared", { thing: "foo" }, [1, 2, 3])
```

The precise behavior of these methods depends on the provider, but the messages must be accessible to scene developers debugging their code.

{% hint style="info" %}
In the Foundation's browser-based World Explorer, log messages appear in the developer tools panel.
{% endhint %}

### Imports and Exports <a href="#module" id="module"></a>

Scenes can import and export objects using the traditional [CommonJS](https://wiki.commonjs.org/wiki/Modules/1.0) module interface.

```ts
exports: Object
require(moduleName: string): Object
```

The `require` function allows scenes to access runtime-provided modules (such as [EngineApi](https://github.com/decentraland/docs/blob/main/contributor/modules/engine_api.md) or [RestrictedActions](https://github.com/decentraland/docs/blob/main/contributor/modules/restricted_actions.md)), and nothing else (it **does not** access NPM packages or modules by path).

Properties added to the `exports` object are the scene's public interface and will be exposed to the runtime. In fact, scenes *must* expose at least one method to run properly (see [execution](https://github.com/decentraland/docs/blob/main/contributor/execution.md)).

{% hint style="info" %}
Scenes written in languages such as TypeScript use the more modern `import` and `export` statements, which can be transpiled into CommonJS-compatible uses of `require` and `exports`.
{% endhint %}

### HTTP and WebSockets <a href="#http" id="http"></a>

The `fetch` and `WebSocket` globals work exactly like their well-known counterparts (see [fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API) and [WebSocket](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API) in MDN), but with some restrictions enforced by the runtime.

When calling the `fetch` function:

* An error is thrown if the URL doesn't begin with `https://`.
* An error is thrown if the scene doesn't have the [`USE_FETCH` permission](https://github.com/decentraland/docs/blob/main/contributor/contributor/content/entity-types/scenes.md#permissions).
* An implementation-defined timeout can abort the request.

When using the `WebSocket` class:

* An error is thrown if the URL doesn't begin with `wss:`
* An error is thrown if the scene doesn't have the [`USE_WEBSOCKET` permission](https://github.com/decentraland/docs/blob/main/contributor/contributor/content/entity-types/scenes.md#permissions).

Apart from these differences, both cases follow standard behavior.


---

# 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.decentraland.org/contributor/scene-runtime/globals.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.