Carlo is a framework for rendering Node data structures using Chrome browser.


Project Name carlo Project Url
InceptionYear 2018-10-29 18:50:04 更新时间 2019-03-19 14:20:47
IssueManagement Licenses Apache-2.0
仓库地址 git+ 用户数 0
Node Engine >=7.6.0 文件大小 23.9 KB
install lint test headful-test


# Carlo - headful Node app framework [![NPM carlo package](]( [![Install Size](]( > Carlo provides Node applications with [Google Chrome]( rendering capabilities, communicates with the locally-installed browser instance using the [Puppeteer]( project, and implements a remote call infrastructure for communication between Node and the browser. ###### [API]( | [FAQ](#faq) | [Contributing]( ![image]( ###### What can I do? With Carlo users can create hybrid applications that use Web stack for rendering and Node for capabilities: - For Node applications, the web rendering stack lets users visualize the dynamic state of the app. - For Web applications, additional system capabilities are accessible from Node. - The application can be bundled into a single executable using [pkg]( ###### How does it work? - Carlo locates Google Chrome installed locally. - Launches Chrome and establishes a connection over the process pipe. - Exposes a high level API for rendering in Chrome with the Node environment. ## Usage Install Carlo #### npm ```bash npm i carlo # yarn add carlo ``` > Carlo requires at least Node v7.6.0. **Example** - Display local environment Save file as **example.js** ```js const carlo = require('carlo'); (async () => { // Launch the browser. const app = await carlo.launch(); // Terminate Node.js process on app window closing. app.on('exit', () => process.exit()); // Tell carlo where your web files are located. app.serveFolder(__dirname); // Expose 'env' function in the web environment. await app.exposeFunction('env', _ => process.env); // Navigate to the main page of your app. await app.load('example.html'); })(); ``` Save file as **example.html** ```html ``` Run your application: ```bash node example.js ``` Check out [systeminfo]( and [terminal]( examples with richer UI and RPC-based communication between the Web and Node in the [examples]( folder. ## API Check out the [API]( to get familiar with Carlo. ## Testing Carlo uses [Puppeteer]( project for testing. Carlo application and all Carlo windows have corresponding Puppeteer objects exposed for testing. Please refer to the [API]( and the [systeminfo]( project for more details. ## Contributing to Carlo Look at the [contributing guide]( to get an overview of Carlo's development. ## FAQ #### Q: What was the motivation behind this project when we already have Electron and NW.js? How does this project differ from these platforms, how does it achieve something that is not possible/harder with Electron or NW.js? - One of the motivations of this project is to demonstrate how browsers that are installed locally can be used with Node out of the box. - Node v8 and Chrome v8 engines are decoupled in Carlo, providing a maintainable model with the ability to independently update underlying components. Carlo gives the user control over bundling and is more about productivity than branding. #### Q: Can a Node app using Carlo be packaged as a Desktop app? The [pkg]( project can be used to package a Node app as a Desktop app. Carlo does not provide branding configurability such as application icons or customizable menus, instead Carlo focuses on productivity and Web/Node interoperability. Check out the [systeminfo]( example and call `pkg package.json` to see how it works. #### Q: What happens if the user does not have Chrome installed? Carlo prints an error message when Chrome can not be located. #### Q: What is the minimum Chrome version that Carlo supports? Chrome Stable channel, versions 70.* are supported.


GroupId ArtifactID Version 引用量
TJ Holowaychuk debug 4.2.0 33676
The Chromium Authors puppeteer-core 5.3.1 372


GroupId ArtifactID Version 引用量
The Chromium Authors @pptr/testrunner 0.8.0 4
The Chromium Authors @pptr/testserver 0.5.0 0
Nicholas C. Zakas eslint 7.10.0 238059