FullStacked

Code, run and share JavaScript projects anywhere: Node’s APIs on every device, iOS and Android included.

FullStacked is a runtime for projects written in TypeScript and JavaScript. A project imports node:fs, node:net or node:crypto, uses npm packages, and draws its UI with the DOM, all in the same file. FullStacked bundles and runs it on macOS, Windows, Linux, iOS, iPadOS, Android and ChromeOS, or from a terminal with Node.

It works without shipping Node or a JavaScript engine. The project runs in the platform’s own webview, and everything a webview can’t do (files, sockets, DNS, compression, cryptography, bundling, npm installs, git) is done by a Go core that the webview reaches through the bridge.

Start here

• Getting started: install the app or the CLI and run a first project.
• Project structure: entrypoint, build output, static files, dependencies, environment, workers.
• CLI: the fullstacked command.

How it works

• Architecture: the core, the hosts, contexts, the sandbox and the platforms.
• The bridge: the wire format, the transports on each platform, streams, frames and workers.

Reference

• Node.js compatibility: every built-in module, what it supports and where it runs.
  • Pure modules: buffer, events, stream, util, assert, …
  • System modules: fs, path, os, process
  • Networking: net, dgram, dns, fetch, WebSocket
  • Crypto and zlib
  • Workers and terminals: worker_threads, readline, tty
  • Unavailable modules: http, child_process, vm, … and what to use instead
• Runtime API: bundle, packages, git, run, config, tunnel, plugin, auth, parentWindow, fullstacked

Contributing

• Building from source: build, test, and add a core function.
• Porting to a new host: the C ABI and what a host implements.

License

FullStacked is MIT licensed. Source: github.com/fullstackedorg/fullstacked.

This site is open source. Improve this page.