This is the most common approach for pure browser applications. You include the library via CDN or a bundler (Webpack/Vite).
It is important to distinguish the (often associated with MercuryWorkshop on GitHub ) from Scramjet.org . scramjet browser work
: It is most stable on Chrome ; other browsers may experience glitches. This is the most common approach for pure
npm install -g scramjet-browser
While traditional proxies operate at the network level by simply routing traffic through an external server, Scramjet handles processing directly within the client browser application. By leveraging modern browser APIs, WebAssembly (WASM), and service worker architectures, Scramjet intercepts, rewrites, and sandboxes web traffic in real-time. Core Architectural Pillars : It is most stable on Chrome ;
: The Scramjet service worker captures the HTTP fetch request before it exits the client browser application.
Scramjet sandboxes web content, which means it isolates the content from the user's main environment. This allows for safe interaction with potentially dangerous sites, as the harmful content cannot easily escape the isolated, proxied environment. Scramjet vs. Traditional Proxies