jscore

jscore is a relatively safe bindings to JavaScriptCore originally written by Apple, and patched by the Bun team.

It is currently in development and is not yet meant for production use.

Feel free to contribute! I finally learned how to use git.

use jscore::prelude::*;

// Create a context group for managing contexts
let group = ContextGroup::new();

// Create the global context for JS interactions
let global = group.create_global_context();
let ctx = global.as_context();

// Create a script
let content = JsString::new("(() => 'hello from js!')()");
let script = Script::builder().script(&content).build();

let result = script.evaluate(ctx).expect("failed to run script");
let result = result
    .to_string_copy(ctx) // We need to copy it or it might get garbage collected
    .unwrap()
    .to_rust_string()
    .unwrap();

println!("{result}");
// Output: hello from js!

Building

The build script (build.rs) is a Rust port to Bun's CMake script. While build tests are successful, it might not build on your machine due to the lack of libraries. If you encounter any problem, feel free to create/view issues because other people might experience the same!

Platform-specific behaviors:

• macOS: Downloads WebKit and builds from it. Currently, it links icucore dynamically and not statically.
• Linux: Downloads WebKit and builds from it.
• Windows: Downloads WebKit, builds ICU from source, then builds from them.

Downloading WebKit:

The script downloads releases from oven-sh/WebKit either with curl or python3, depending on what's available.

AI notice

I do have to admit that I co-created the build script with the help of artificial intelligence as I do not have this area of expertise, meaning the code quality may be concerning. However, I do want to point out that I don't agree with mass, unprocessed & unaudited AI use, and I did not use AI when creating the Rust bindings; they're hand written.

Update: Yeah I dominated the code base. Less AI slop. Yay!