It's possible or maybe a good option, to use ts2fable to generate partial types from @types/node?

Hi,
since we're moving out of the "tinkering with Fable and Node.js" side with these brand new bindings, what do we want to support?

I started revamping APIs to support LTS and maybe new experimental features. But do we need to support legacy, pre 10.x as well? (Node.js 6? Nodejs 8?).

their is no bindings for options argument passed to fs.mkdirSync with

 fs.mkdirSync ("temp/db", { recursive: true, mode: "mymode" })

https://nodejs.org/api/fs.html#fs_fs_mkdir_path_options_callback

Node provides TextEncoder class that implements the same interface as the browser api in a "util" namespace util.TextEncoder as well as a global object.

We have been keeping track of the progress to publish all libraries to Fable.Core 3.0 stable. Looks like package is still on the beta version. Can you please release a stable version too? if not, what is needed and how can I help?

Cheers

No Console types found so far in the API. Is it something that was just missing or left out on purpose?

@MangelMaxime @nojaf @whitetigle I've ported the bindings from fable-import. You should have write access to this repository.

I've tried to do something similar to fable-browser namespaces. However in this case all modules need to be qualified to prevent name conflicts. But now you only need to open Node to start invoking modules.

I've removed interfaces already included in Fable.Core.JS and replaced Function with ('FIn->'FOut) but there may be a better solution for that.

It's building but I haven't tested it, please have a look and feel free to change anything (I've also added a couple of other issues as ideas to improve the bindings). Then you can publish the package with the Fable.Node id :)

The typescript node typings are more up to date and ts2fable could generate all bindings, no?