Rollup Browser Build

assert> ​

Browser Build

Uses only browser APIs, installable via npm install @rollup/browser.

--bundleConfigAsCjs ​

Caveats when using native Node ES modules ​

CDN import

Import ESM or UMD builds from a CDN such as unpkg, creating a global window.rollup.

Command line flags ​

Command Line Interface

Config Intellisense ​

--configImportAttributesKey <with

Configuration Files ​

Differences to the JavaScript API ​

Getting the current directory ​

Importing package.json ​

In-memory file system

Provide an in-memory fs implementation via the fs option implementing a subset of the NodeJS fs API.

In-memory filesystem

Provide a memory filesystem implementing a subset of the NodeJS fs API via the fs option.

In-Memory File System

Provide an in-memory fs via the fs option implementing a subset of the NodeJS fs API.

Loading a configuration from a Node package ​

Plugin-based resolution

Resolve and load all modules via plugins instead of the file system.

Plugin-based module resolution

Resolve and load modules using plugins when no filesystem is available.

WASM binding

Requires serving dist/bindings_wasm_bg.wasm alongside the browser build.

WASM Bindings

Requires dist/bindings_wasm_bg.wasm to be served next to the browser build.