Import C++ and Rust
like JavaScript modules.

No bindings, no glue, no second build system. One import runs in the browser, on iOS and Android, in Node, on Workers, and as a WASI command.

Get started

Free and open source under the MIT license.

src/main.js

import { initNative, Matrix } from './native/Matrix.h';
import { GDALVersionInfo } from '@crossbind/port-gdal/gdal.h';
 
await initNative();
 
const a = new Matrix(1210000, 1);
const b = new Matrix(1210000, 2);
const result = a.multiple(b);
 
console.log(result.get(0), GDALVersionInfo('RELEASE_NAME'));

src/main.js

import { initNative, Uuid } from 'cargo:uuid';
import { Version, VersionReq } from 'cargo:semver';
 
await initNative();
 
const id = Uuid.newV4().toString();
const ok = new VersionReq('^1.2').matches(new Version('1.4.0'));
 
console.log(id, ok);

✓SAME CODE · FIVE RUNTIMES

Browser

Chrome · Firefox · Safari

Node.js

CJS or ESM

React Native

iOS + Android · JSI

CF Workers

Edge · single-threaded

WASI

wasmtime 47+ · wasip3

LIVE · SQLITE, COMPILED BY CROSSBIND

Query a real C library, here.

This page boots the published SQLite port, seeds an in-memory database with its own library catalog and runs whatever you type. No server answers these queries.

SQL

first run downloads 1.5 MB of WebAssembly

src/native/database.h

#include <sqlite3.h>
 
class Database {
public:
    Database() { sqlite3_open(":memory:", &handle); }
    ~Database() { sqlite3_close(handle); }
 
    void exec(const std::string& sql);
    std::string query(const std::string& sql);
 
private:
    sqlite3* handle = nullptr;
};

src/main.js

import { initNative, Database } from './native/database.h';
 
await initNative();
const db = await new Database();
 
await db.exec(catalogAsSql);
const rows = await db.query(yourQuery);

The database lives in this tab and nothing is uploaded. The wrapper is forty lines; the rest is upstream SQLite, precompiled. Libraries has the install flow.

Start fresh in under a minute.

The scaffolder asks five questions and prints a working repo — framework, bundler, target, and a sample C++ binding already wired. npm run dev works on the spot.

RUN

npm create crossbind@beta

FRAMEWORKS

ReactVueSvelteVanilla

BUNDLERS

ViteRspackWebpackRollupMetro

TARGETS

Web (WASM)React NativeNode.jsCloudflare Workers

terminal · ~/projects
> npm create crossbind@beta

FULL CAPABILITY MATRIX

26 capabilities · 9 platform details

Write it

The native API you expose to JavaScript

01Bindings you never write 02Rust through the same import 03Native code that calls you back 04TypeScript, generated 05Hot reload for C++ & Rust

Resolve it

How packages become a target-ready dependency graph

06The whole native graph, resolved 07The right artifact for this target 08Prebuilt first. Source when you ask.09Rebuild one dependency, not all of them

Build it

How source turns into every required target

10One command, the full build matrix 11CMake, Autotools or your own runner 12No toolchain to install 13Nothing rebuilds twice 14Only what you use 15Override anything

Run it

Where the same API executes

16One codebase, every platform 17On-device by default 18Off the main thread 19Big files, browser and Node

Ship it

What reaches apps, npm and the command line

20One graph, every artifact 21Libraries as npm dependencies 22Data files, auto-wired 23Ship a CLI, no JavaScript

Trust it

What you can inspect before depending on it

24A supply chain you can audit 25You can see what it did 26Tested on the platforms it claims

Also in the box: Expo config plugin, memory64 targets, JSPI async (experimental), SWIG escape hatch, Android arm64 + x86_64, monorepo paths, write your own bundler plugin, CommonJS + ESM modules, clean dependency cache command.

PREBUILT LIBRARIES