Deno has some JavaScript/TypeScript in it. On GitHub https://github.com/denoland/deno is 22.8% JavaScript and 13.2% TypeScript, and https://github.com/denoland/deno_std is 68.2% JavaScript and 31.6% TypeScript.
So to me the title is misleading about the name (Deno is certainly not named Deno.js), but not about what Deno is written in.
> git clone https://github.com/denoland/deno.git denoland/deno
> git clone https://github.com/denoland/rusty_v8.git denoland/rusty_v8
> cd denoland/deno
> vi Cargo.toml
...
[patch.crates-io]
rusty_v8 = { path = "../rusty_v8" }
...
> cargo build --release
... as expected same failure - good ...
Make rusty_v8 build.rs aware of freebsd > vi ../rusty_v8/build.rs
...
#[cfg(target_os = "freebsd")]
{
"freebsd"
}
...
Have a quick squizz to see where this is used: > rg "platform\(\)" ../rusty_v8
build.rs
157:fn platform() -> &'static str {
180: .join(platform());
Attempt to fix... and bang! It's using the platform() result to call a python script that pulls binaries from here:https://github.com/denoland/ninja_gn_binaries/
And there's no FreeBSD build there. To much yak shaving for idle curiosity on my part.
Two random Rust projects:
https://github.com/tokio-rs/tokio:
$ grep -irn 'unwrap' | wc -l
1398
https://github.com/denoland/deno: $ grep -irn 'unwrap' | wc -l
2050
I dunno, but all Rust projects I have encountered had unwraps everywhere.I'm really hopeful about deno (https://github.com/denoland/deno) for this. TypeScript is nice, the deno TCP perf is good, all it needs is some good proxy libraries.
interesting thanks for the heads up - my assumption is though that this is just a wrapper over a V8 engine with typescript compilation on the fly?
Does that make it a TypeScript runtime or not?