Yantra (Machine in Sanskrit) is a Managed JavaScript Engine for .NET Standard written completely in C#.
Name | Package |
---|---|
YantraJS (With CSX Module Support) | |
YantraJS.Core (Compiler) | |
YantraJS.ExpressionCompiler (IL Compiler) | |
Yantra JS.ModuleExtensions (Fluent interface for module registration) |
- Compiles JavaScript to .Net Assembly
- Strict Mode Only JavaScript*
- Arrow functions
- Classes
- Class members
- Enhanced object literals
- Template strings and tagged templates
- Destructuring
let
const
- Map, Set, WeakMap, WeakSet
- Symbols
- Subclassable built-ins
- Binary and Octal literals
- Module support
- Null coalesce
- Optional property chain
identifier?.[]
,identifier?.(
,identifier?.identifier
- Rest, Default and Spread Parameters
- Generators, iterators, for..of
- Async/Await
- Optional parameters
- Tail call optimization
- Many ES5 + ES6 features
- CommonJS & ES6 Module Support
- Easily marshal CLR Object to JavaScript and other way around
- CSX Module support
- Mixed module system, YantraJS supports
require
andimport
. - Explicit resource management with
using
andawait using
keywords.
*
Most JavaScript today is available in strict mode, we do not feel any need to support non strict mode as modules are strict by default.
Currently YantraJS supports Both CommonJS and ES modules without any extra work, with little trick, module resolution is node like
. Module loader loads module asynchronously, so import
will work without any extra effort. However, require
will run AsyncPump
to wait till the module is loaded correctly. Unless you do some multithreading, mixed modules will not lead to any deadlocks.
- Module names may or may not have extensions.
- File will be loaded if same name exists on disk.
- Engine will try to load
${name}.csx
file, if it exists it will load the module. - Engine will then try to load
${name}.js
file, if it exits it will load the module. - Otherwise it will travel to parent directory and search modules in
node_modules
folder in exact same order defined earlier.
As we often have difficulty in writing cross environment scripts (browser and process such as node), we want to first implement basic common features on both.
- Generate Runtime with Source Generator, this will allow us to load Yantra in AOT environment. Currently Runtime objects are loaded through reflection, however we are moving reflection code to Source Generator one class a at a time.
- Next in plan is Network API, Simple
fetch
is available inYantraContext
, we will focus on adding Stream API. - Next is File API, we will implement
FileSytem
of Web Browser API and allow an easy native interface. So you can write script that will execute correctly in browser and in native - V8 Protocol Implementation is in progress.
We recommend using Github Discussion on this repository for any question regarding this product.
- We are thankful to authors of Jurassic (we have incorporated number parser, promise and some unit tests from Jurassic.) https://github.com/paulbartrum/jurassic
- We are thankful to authors of EsprimaDotNet, we initially built prototype over EsprimaDotNet, but we chose to build our parser/scanner from scratch to support token spans. https://github.com/sebastienros/esprima-dotnet
- We are thankful to author of ILPack (we have incorporated saving IL to Assembly from this library.) https://github.com/Lokad/ILPack