feat(neon): Node stdlib

[dherman]

Experimental API for convenient access to the Node stdlib.

Examples:

use neon::node::Node;

// ...

cx.console().log("hello, world!")?;

// ...

let versions = cx.process().versions()?;
println!("node version: {}", &versions.data().node);

[kjvalencik]

TryIntoJs will cover logging things that aren't string, but console.log(..) is also variadic. Thoughts on how we cover that? Could we use the TryIntoArguments trait?

It would be interesting to explore what a log macro would look like. 🤔 Something tricky in a macro is disambiguating between format arguments and distinct arguments to log.

[dherman]

Here’s what my thinking was, but tell me what you think:

I was thinking, you can get the most general behavior from the JS values, but the goal here is convenient and idiomatic Rust syntax for the most common functionality. So I figure the highest value is getting the cx.console().log(x) syntax, and the variadic use case is less important.