node package manager

engify

Build Status

What's this?

Browserify transformation that add minimal support for running node.js projects in multiple JavaScript implementations:

  • node
  • browser
  • rhino
  • Nashorn
  • spidermonkey (https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey)
  • JavaScriptCore (http://webkit.org - safary)
  • ringojs (http://ringojs.org/)
  • v7

Particularly it adds support for non standard:

  • console.log
  • global object

Right now is just an idea and experiments

The objective is alsbeing able and test other javascript implementations other than just node and the browser. Let's see how well we can "program once" run everywhere in JavaScript works...

Examples

Ultimately this project contains lots of example projects that will compile into a .js file that run on all above implementations.

They not only uses different npm libraries but also browserify tools and languages like es-6 babel, typescript, etc.

Usage

Assuming you have a node.js working project:

npm install engify
browserify -t engify index.js -o output.js
rhino output.js
jsc output.js

Libraries tested

The following are libraries that I were able to use in all implementations:

  • underscore
  • lodash
  • momentjs
  • esprima
  • escodegen
  • handlebars

browserify transformations tested

In general all browserify transformations should work! :) - in my case they all worked:

  • hbsify
  • brfs
  • tsify
  • coffeeify
  • browserify-livescript

Objectives

  • Be able to write code using npm and run it in all javascript implementations.
  • support some very basic apis in all the impls, like console.log and the global object.
  • try to run js libraries that currently support browser and node like underscore, momentjs, esprima, lodash, acorn, etc in the rest of the implementations.

Interesting commands

#run tests - located at spec/ folder
npm test

#run a tool that compiles a project and run it in all the implementations: 
sh test-project.js projects/handlebars-test

#compile sample project test-src: into a bundle
node src/index.js --input test-src/index.js > static/output.js

#run in node
node output.js

#run in Nashorn
jjs output.js

#run in rhino
rhino output.js

#run in v7 [v7](https://github.com/cesanta/v7)
v7 output.js

#compile and run in the abobe in a single command: 
sh test/test1.sh

#execute them all
node static/output.js; rhino static/output.js ; jjs static/output.js ; v7 static/output.js

# measure time:
time node static/output.js; time rhino static/output.js ; time jjs static/output.js ; time v7 static/output.js

Release Tests

On any commit we should make the following commands work:

git clone https://github.com/cancerberoSgx/engify.git
cd engify
npm install

cd test-src
npm install
cd ..    
sh test-project.sh test-src

This last command will build givven test-src/index.js into static/ folder and then run it with all supported engines in the command line.

TODO /Misc

  • support browser!
  • try windows native javascript engines (http://superuser.com/questions/488763/how-to-run-js-file-from-a-command-line-on-windows)
  • move file ../../test-src/js-compat to separate project
  • put global and console.log in a commons-js module
  • bin program: engify my/project/services/service1.js > output.js
  • Should be a browserify transformation ? currently not just uses browserify js api. write it anyway : (from https://github.com/substack/browserify-handbook)
  • put test-src as a separate project
  • browserify experiment: load libraries in ssp-libraries files and be able to use require() directly in .ss / scripts. probably i need to use a browserify flag.
  • try writing client side suitescript & jquery using Function.prototype.toString