Scram.js

Introduction

Scram.js offers a simple way to use Electron as a platform for universal web components, allowing you to use HTML, Web APIs, and virtually any other client-side tool to write server-side and even embedded applications. If you have not heard of web components, then please start learning today. Web components offer a way to manage complexity and expose it simply, by allowing you to create reusable components that can be easily shared and composed to create entire applications. Currently they are used mostly for front-end web development. What about non-visual applications? Web components are not only useful for visual components, but offer many benefits for building all kinds of user interface applications. We are one step closer to true Universal JavaScript.

This repo only offers access to the runtime necessary to use server-side web components. To actually begin building applications, you'll need components to work with:

Server-side Web Components

* Express Web Components: https://github.com/scramjs/express-web-components

Embedded Web Components

* JFive Web Components: https://github.com/scramjs/jfive-web-components

Examples

Here are some example Express.js apps that have been rewritten with web components:
* https://github.com/scramjs/rest-api-express
* https://github.com/scramjs/node-api
* https://github.com/scramjs/node-todo
* https://github.com/scramjs/node-tutorial-2-restful-app
* https://github.com/scramjs/node-tutorial-for-frontend-devs

Here are some example hardware apps that have been written with web components:

* https://github.com/scramjs/web-copter

For more background information, see the following resources:
* Universal Web Components article
* Universal Web Components video presentation
* Server-side Web Components article
* React Hardware article

Development Installation

``bash
npm install scram-engine
`

Production Installation

There are a few more considerations in a production environment. Since Electron needs a graphical environment for rendering on headless Linux® machines, you may need to install Xvfb to provide a display server.

On Ubuntu: sudo apt-get install xvfb

The Electron dependency might require one or more of the following libraries to be installed on certain Ubuntu systems:

`
libgtk2.0-0
libnotify-bin
Libgconf-2-4
libxss1
`

The NGINX dependency might require one or more of the following libraries to be installed:

`
libpcre3
libpcre3-dev
`

$3

Scram.js works well with Dokku. Dokku provides a personal PaaS, making it easy to deploy to a production server environment.
* Follow the official documentation to install Dokku
* Install this Dokku plugin to allow Dokku to automatically install Xvfb and other packages your application might need
* Add a file to the root directory of your app called apt-packages
* List the packages you would like Dokku to install: e.g. xvfb libgtk2.0-0 libnotify-bin Libgconf-2-4 libxss1
* Ensure that dependencies are listed correctly in your app's package.json
* Add a start script in your app's package.json for Dokku to use to start your application
* Add an engines property to your app's package.json to specify the version of node Dokku will use to run your app
* For a full working example of an application deployed with Dokku, see the Dokku Example

Usage

$3

Provide Electron with the main.js script from this repo and then the path to your starting html file from the root directory of your app:

node_modules/.bin/electron node_modules/scram-engine/main.js --entry-file index.html

It might be convenient to create a script in your package.json:

`JSON
{
"name": "awesome-repo",
"version": "2.4.2",
"scripts": {
"start": "electron node_modules/scram-engine/main.js --entry-file index.html"
}
}
`

To open up an Electron window for access to the dev tools, add the --window or -w option:

node_modules/.bin/electron node_modules/scram-engine/main.js --entry-file index.html --window

or

`JSON
{
"name": "awesome-repo",
"version": "2.4.2",
"scripts": {
"start": "electron node_modules/scram-engine/main.js --entry-file index.html --window"
}
}
`

$3

You need to add the xvfb-run command in front of all other commands on headless Linux machines:

xvfb-run node_modules/.bin/electron node_modules/scram-engine/main.js --entry-file index.html

It might be convenient to create a script in your package.json:

`JSON
{
"name": "awesome-repo",
"version": "2.4.2",
"scripts": {
"start": "xvfb-run electron node_modules/scram-engine/main.js --entry-file index.html",
"dev": "electron node_modules/scram-engine/main.js --entry-file index.html",
"dev-window": "electron node_modules/scram-engine/main.js --entry-file index.html --window"
},
"engines": {
"node": "6.0.0"
}
}
``

$3

#### Loading Start File
It is important to understand the two different ways in which your starting html file is loaded into Electron, as each has subtle differences in behavior:

##### Local Server
By default, unless you add the -f option when starting the application, the specified starting html file is loaded into an Electron BrowserWindow from a local http server running on the following address: 0.0.0.0:5050. The port can be changed with the -p option. Loading the starting html file from a local server allows your server-side application to emulate a client-side application more faithfully. For example, client-side requests that rely on the protocol of their environment will have the protocol set to http and the domain to localhost, making life much easier than trying to do the same thing with the protocol set to file.

Loading the starting html file from a local server will cause __dirname and __filename to be incorrect for any web components included from your starting html file. You must include filesystem-config.js before any code that relies on __dirname or __filename to correct those issues.

##### Filesystem
The -f option will allow you to load your starting html file from the filesystem. Be aware that this may cause issues if you are using client-side code because the protocol is set to file.

##### Require
Any relative requires should be done relative to the starting html file when requiring from within an imported web component. When requiring from within a required module, relative requires should be done relative to the module (normal require behavior).

##### __dirname and __filename
__dirname and __filename are set relative to the starting html file, and should be the same across all components imported throughout your application. __dirname referenced directly from a web component script will be set to the absolute path of the directory that your starting html file resides in. __filename referenced directly from a web component script will be set to the absolute path of the starting html file, including that file's name.

__dirname and __filename inside of required modules act as expected.

When loading the starting html file from the local server, you must include the filesystem-config.js file before referencing __dirname or __filename in any imported web components:

`HTML

`

Do not include this file when loading the starting html file from the filesystem.

$3

There are various options available when loading your application:

* --entry-file: The HTML file to load into Electron
* --window or -w: Open a browser window for debugging
* --file-system or -f: Load the starting html file from the filesystem
* --port or -p: Specify the port the local server uses to load the starting html` file

Compatibility and Testing

Only manually tested at the moment. PR with tests if you'd like :)

Node.js is a trademark of Joyent, Inc. and is used with its permission. We are not endorsed by or
affiliated with Joyent.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.