Carlo provided 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.
All functions that you see here got ported over to Puppeteer to make installation and usage more easy in general every one who learned about Browser Automation in general got a solid foundation.
It is as it is with linux. Your good at linux as soon as you understand the tooling and how to pipe them together. Same is true for DWeb and ECMAScript which powers the DWeb.
API | FAQ | Contributing
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.
- 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.
Install Carlo
npm i @component-manager/node
# yarn add carloCarlo requires at least Node v7.6.0.
Example - Display local environment
Save file as example.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
<script>
async function run() {
// Call the function that was exposed in Node.
const data = await env();
for (const type in data) {
const div = document.createElement('div');
div.textContent = `${type}: ${data[type]}`;
document.body.appendChild(div);
}
}
</script>
<body onload="run()">Run your application:
node example.jsCheck out systeminfo and terminal examples with richer UI and RPC-based communication between the Web and Node in the examples folder.
Check out the API to get familiar with Carlo.
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.
Look at the contributing guide to get an overview of Carlo's development.
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.
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.
Carlo prints an error message when Chrome can not be located. Soon it will point you to install it.
Chrome Stable channel, till dev-channel so nightly