An ES5 interpreter for Java
Go to file
2023-12-24 14:40:27 +02:00
.github/workflows fix: some annoying bugs, as well as splice 2023-11-06 00:55:30 +02:00
src fix: correctly convert virtual to real path 2023-12-24 14:40:27 +02:00
tests feat: write some tests 2023-11-04 11:38:48 +02:00
.gitattributes fix: some config files cleanup 2023-12-24 14:31:33 +02:00
.gitignore fix: some config files cleanup 2023-12-24 14:31:33 +02:00
build.js fix: don't include ts's code in repo anymore 2023-12-24 14:32:37 +02:00
LICENSE bruh 2023-08-26 12:19:26 +03:00
README.md fix: remove major mistakes in README 2023-12-24 14:31:50 +02:00

JScript

NOTE: This had nothing to do with Microsoft's dialect of EcmaScript

WARNING: Currently, this code is undocumented. Proceed with caution and a psychiatrist.

JScript is an engine, capable of running EcmaScript 5, written entirely in Java. This engine has been developed with the goal of being easy to integrate with your preexisting codebase, THE GOAL OF THIS ENGINE IS NOT PERFORMANCE. My crude experiments show that this engine is 50x-100x slower than V8, which, although bad, is acceptable for most simple scripting purposes. Note that although the codebase has a Main class, this isn't meant to be a standalone program, but instead a library for running JavaScript code.

Example

The following is going to execute a simple javascript statement:

var engine = new Engine(false);
// Initialize a standard environment, with implementations of most basic standard libraries (Object, Array, Symbol, etc.)
var env = Internals.apply(new Environment());

// Queue code to load internal libraries and start engine
var awaitable = engine.pushMsg(false, env, new Filename("tmp", "eval"), "10 + Math.sqrt(5 / 3)", null);
// Run the engine on the same thread, until the event loop runs empty
engine.run(true);

// Get our result
System.out.println(awaitable.await());

NOTE:

To setup the typescript bundle in your sources, run node build.js init-ts. This will download the latest version of typescript, minify it, and add it to your src/assets folder. If you are going to work with the node build.js debug|release command, this is not a necessary step.