scriptit

scriptit is a simple way to run JavaScript code in Rust

scriptit will run your JS differently depending on your platform:

• Run in a V8 interpreter for "native" targets
• Run in the WASM host interpreter for "wasm32" targets

Why?

I wanted to be able to do scripting in my rust applications, I do not need a fully-fledged embedding of v8 like node or deno and the only use here is as a library, so you get to choose what to inject.

Additionally I want to write most of my rust apps with a possible wasm target: as we likely have a js engine when running rust code on wasm targets, I thought about using the js interpreter on the host. This makes scriptit an extremely lightweight way to run scripts in wasm as we use host capabilities to do so!

Limitations

Due to those goals, scriptit will not give you the same amount of control that you would have embedding v8 yourself and will give you worst ergonomics than just using wasmbindgen. It is unfortunately ruled by common denominators on both apis (v8 & wasmbindgen).

Example

```rust use scriptit::{ core::value::ScriptValue, ScriptingEnvironment };

let mut s_env = ScriptingEnvironment::new();

let src = " const greeter = 'JS'; const greeted = 'Rust'; Hello ${greeted}! (from ${greeter}...) "; let res = s_env.eval(src).unwrap();

asserteq!(res, ScriptValue::String("Hello Rust! (from JS...)".tostring())); ```

Roadmap

scriptit is extremely experimental, I wouldn't use it for anything now, at least not before the following is done:

• Serializing/Deserializing complex structures to and from js through serde, probably...
• Add the ability to inject Rust functions to the global object to enable calls to rust from JS
• ES Modules support

See the issues for more details.