How frnlol/frn works
The repository appears to be a browser-based web proxy/runtime, with a service-worker layer routing proxied requests and a frame-side client that initializes the rewriting engine and communicates with that worker. A separate extension subsystem serves locally stored extension files. The tree also includes a large application bundle and a signed-release service worker, but the README is empty and the bundle and main runtime excerpt are incomplete; several product capabilities and links therefore cannot be established confidently.
Main entry points: 70wt6c.js Frame client · bundle-1oxptspd.js Web application · thnd7d.js Frame controller · rbe2ea.js Proxy service worker
Components 11
Proxy Runtime
- Proxy service worker
b/zqz5g/rbe2ea.js - Frame client
b/zqz5g/70wt6c.js - Frame controller
b/zqz5g/thnd7d.js - Proxy engine
b/k18qb/93ngke.js
Extensions
- Extension router
b/irvrg0.js - Extension database
b/tqctx9.js
Release Runtime
- Release service worker
v7m.js
Application Assets
- Web application
b/assets/bundle-1oxptspd.js - Application datasets
b/assets/json
Other components
- Browser user
- Release sources
Connections 10
- Browser user → Web application: uses
- Web application → Frame controller: creates frame
- Frame controller → Frame client: injects client
b/zqz5g/thnd7d.js - Frame client → Proxy engine: loads engine
b/zqz5g/70wt6c.js - Frame client → Proxy service worker: initializes transport
b/zqz5g/70wt6c.js - Proxy service worker → Frame controller: dispatches transport
- Browser user → Extension router: requests extension files
- Extension router → Extension database: reads files
b/irvrg0.js - Release service worker → Release sources: fetches releases
v7m.js - Web application → Application datasets: loads datasets