Carlo development on a Web serverby@agney

Carlo development on a Web server

by Boy with Silver WingsJanuary 6th, 2019
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

<a href="">Carlo</a> is a headful Node app framework for building desktop applications.

Company Mentioned

Mention Thumbnail
featured image - Carlo development on a Web server
Boy with Silver Wings HackerNoon profile picture

Originally posted on

Carlo is a headful Node app framework for building desktop applications.

How is it different from Electron, Proton Native?

While these other frameworks, bring their own runtime into the equation, Carlo uses the Chrome instance already installed on a users computer.

Why would you want it on a web server?

Using webpack to bundle all your files makes it easier to use the developer ecosystem that the javascript community already provides. Like Babel, SCSS or ESLint.

What is about to be assumed?

You already know how to setup a normal webpack server.

Is there a shortcut?

Yes, Electrojet CLI provides a single command to setup a carlo project using webpack:

npm init electrojet <project-name> --template=carlo

How do I set Carlo to listen to the webpack dev server?

Carlo has an API serveOrigin to listen to a particular web address as origin. You can use that with:

carlo.launch().then(async app => {
  app.on('exit', () => process.exit());
  app.serveOrigin('http://localhost:8080'); // Point to webpack url here
  await app.load('index.html');

But then, you would soon find that your javascript bundle is not loading.

What is the problem?

Carlo, currently on version 0.9, allows to serve origin contents only when they are from secure origins, which means if you try to setup a normal webpack server to serve the application you would end up with:

Blocked by the Client

in the console while serving the application.

Fortunately, if you are using webpack dev server, the solution to this is easy. Inside the configuration object for devServer provide:

  devServer: {
    http: true,

But this would pull up the nasty Your webpack is not secure screen for you, when you are not even running it on a webpage.

Luckily, Carlo provides an API to escape this dreaded screen. On launching the carlo server, you can provide args: ["--allow-insecure-localhost"], to avoid seeing the screen ever again.

  args: ["--allow-insecure-localhost"],

You should have your server up and running now.

Check out Electrojet Carlo Default

Happy Coding!