Node.js Support in App Functions

Overview

App Functions are executed in a V8 isolate runtime, which is a lightweight and secure environment. This runtime is distinct from a full Node.js environment. Consequently, while App Functions support JavaScript, they do not support all the native APIs and core modules that are available in Node.js.

This document outlines the level of support for Node.js features within the App Functions environment.

Unsupported Node.js Core Modules

The following Node.js core modules are not available in App Functions. Attempting to use them will result in an error.

child_process

cluster

dgram

fs

fs/promises

http (for creating servers)

https2

net

repl

readline

tls

worker_threads

zlib (Node.js API)

Examples of Unsupported Usage

Here are some examples of code that will not work in the App Functions environment.

Filesystem Access:

Creating a TCP Server:

Spawning a Subprocess:

Creating an HTTP Server:

Creating a UDP Socket:

Partially Supported Modules

Some Node.js modules are partially supported, meaning that only a subset of their functionality is available.

crypto: Only the Web Crypto API is supported.

buffer: Basic buffer functionality is available.

stream: Only WHATWG streams are supported.

os: Partially supported.

path: Partially supported.

util: Partially supported.

events: Partially supported.

Supported Patterns

While direct Node.js APIs for networking are limited, you can make outbound HTTP requests using the fetch API, which is a standard web API.

External Packages

Currently, App Functions do not support importing external packages or libraries from sources like npm. We are actively working on enhancing the platform to include support for external libraries in future versions.

NodeJs Support

Node.js Support in App Functions#

Overview#

Unsupported Node.js Core Modules#

Examples of Unsupported Usage#

Partially Supported Modules#

Supported Patterns#