bytenode

A minimalist bytecode compiler for Node.js.

This tool truly compiles your JavaScript code into V8 bytecode. It can be used with Node.js >= 6.x.x (or maybe even Node.js v5.7.x), as well as Electron and NW.js (check examples/ directory).

It allows you to hide or protect your source code in a better way than obfuscation and other tricks. I have to say that I'm aware of the counter arguments against this "protect" attitude (for example: 01, 02), but it is still a valid use case and the lack of this feature continues to keep many people from using Node.js.

It's more like how python generates .pyc of .py files, but in Node.js world ( .js > .jsc ).

Install

npm install --save bytenode

Or globally:

sudo npm install -g bytenode

How to use it programmatically?

You have to run node with this flag node --no-lazy in order to compile all functions in your code eagerly. Or, if you have no control on how your code will be run, you can use v8.setFlagsFromString('--no-lazy') function as well.

const bytenode = require('bytenode');

How to compile JavaScript code?

let helloWorldBytecode = bytenode.compileCode(`console.log('Hello World!');`);

This helloWorldBytecode bytecode can be saved to a file. However, if you want to use your code as a module (i.e. if your file has some exports), you have to compile it using bytenode.compileFile(), or wrap your code manually, using Module.wrap() function.

How to run compiled bytecode?

bytenode.runBytecode(helloWorldBytecode);
// Hello World!

How to compile a CommonJS module?

let compiledFilename = bytenode.compileFile('/path/to/your/file.js', '/path/to/compiled/file.jsc');

let compiledFilename = bytenode.compileFile('/path/to/your/file.js');

This function compiles your .js file, saves .jsc to disk, and returns the path to that compiled file /path/to/your/file.jsc.

The second argument is optional, the default behavior is to save the compiled file using the same path and name of the original file, but with .jsc extension.

How to run bytecode compiled file?

bytenode.runBytecodeFile('/path/to/compiled/file.jsc');

This will run your file and whatever bytecode inside it.

let myModule = require('/path/to/your/file.jsc');

Just like regular .js modules. You can also omit the extension .jsc.

.jsc file must have been compiled using bytenode.compileFile(), or have been wrapped inside Module.wrap() function. Otherwise it won't work as a module.

.jsc files must run with the same Node.js version that was used to compile it (using same architecture of course). Also, .jsc files are CPU-agnostic. However, you should run your tests before and after deployment, because V8 sanity checks include some checks related to CPU supported features, so this may cause errors in some rare cases.

Bytenode CLI

  Usage: bytenode [option] [ FILE... | - ] [arguments]

  Options:
    -h, --help                        show help information.
    -v, --version                     show bytenode version.

    -c, --compile [ FILE... | - ]     compile stdin, a file, or a list of files

  Examples:

  $ bytenode -c script.js             compile \`script.js\` to \`script.jsc\`.
  $ bytenode -c server.js app.js
  $ bytenode -c src/*.js              compile all \`.js\` files in \`src/\` directory.

  $ bytenode script.jsc [arguments]   run \`script.jsc\` with arguments.
  $ bytenode                          open Node REPL with bytenode pre-loaded.

Some quick examples:

Compile express-server.js to express-server.jsc.

user@machine:~$ bytenode --compile express-server.js

Run your compiled file express-server.jsc.

user@machine:~$ bytenode express-server.jsc
Server listening on port 3000

Compile all .js files in ./app directory.

user@machine:~$ bytenode --compile ./app/*.js

Compile all .js files in your project.

user@machine:~$ bytenode --compile ./**/*.js

Note: you may need to enable globstar option in bash (you should add it to ~/.bashrc): shopt -s globstar

Starting from v1.0.0, bytenode can compile from stdin.

$ echo 'console.log("Hello");' | bytenode --compile - > hello.jsc

Todo:

Write some tests.
Add some examples.
Add an Electron example.
Add an NW.js example (NW.js has a similar tool nwjc, which can be used with Client-side JavaScript code See here. Using both tools, you can compile all you code).
Add advanced Electron and NW.js examples.
Benchmark .jsc vs .js.

Acknowledgements

I had the idea of this tool many years ago. However, I finally decided to implement it after seeing this issue by @hashseed. Also, some parts was inspired by v8-compile-cache by @zertosh.

mbnadjib/bytenode