Carlo

Carlo is a Node.js web rendering framework and desktop application bundler. It functions as a server-side browser controller and headless automation bridge that uses a local browser instance as the primary user interface for Node.js applications.

The project distinguishes itself by providing a bidirectional bridge for cross-environment JavaScript integration, allowing server-side functions to be exposed to the browser window object and enabling the execution of page-context code from the server. It includes capabilities for packaging applications into standalone desktop executables, complete with custom window settings and system icon configuration.

The framework covers a broad surface of capabilities, including network request interception, local and remote content serving, and browser instance orchestration. It also provides tools for application window management and a headless test mode for automated verification.

Features

Asynchronous Message-Passing Bridges - Implements a bidirectional bridge for secure, asynchronous message passing between the Node.js server and the browser UI.

Node.js Desktop Frameworks - A framework that uses a local browser instance as a rendering surface for Node.js applications.

Desktop Application Packagers - A tool for packaging Node.js applications into standalone desktop executables with custom window and icon settings.

In-Page Script Execution - Provides the capability to execute JavaScript strings or functions directly within the browser page context from the server.

Browser Function Invocations - Allows server-side JavaScript functions to be injected into the browser window object for direct invocation by the frontend.

JavaScript Execution Bridges - Provides a bridge for executing scripts and invoking functions between a Node.js host and a browser environment.

Web-Based Rendering Engines - Provides a framework for hosting web-based user interfaces within native desktop windows using a local browser instance.

Web Integration Bridges - Connects a web rendering stack with a backend environment to grant applications access to low-level system resources.

Headless Browser Controllers - Uses a local browser instance as a rendering surface, controlled by a server-side Node.js process.

Automation Bridges - A bridge connecting a backend environment to browser page contexts for executing JavaScript and intercepting network requests.

Server-Side Controllers - A controller that manages browser windows and exposes server-side functions to the frontend window object.

Local Directory Serving - Makes local directories available to the browser via specified URL prefixes for asset serving.

Standalone Application Packaging - Packages the web-based application and Node.js runtime into a single-file binary to eliminate dependency on pre-installed runtimes.

Local File Mappings - Maps local directory paths to browser-accessible URL prefixes to serve assets without requiring a full web server.

Standalone Runtime Bundling - Packages the Node.js runtime and browser binaries into a single standalone executable for easy desktop deployment.

Application Window Managers - Provides controls for opening and managing browser windows with specific size and position settings.

Request Interception Middleware - Provides middleware to intercept and modify network requests at the browser level to fulfill resources from the local backend.

Headless Browser Orchestration - Orchestrates the startup of browser instances with configurable dimensions, colors, and user data directories.

GoogleChromeLabscarloArchived

Features

Star history