refactor(bindings)!: convert node bindings to NAPI

[segevfiner]

This is a breaking change that accompanys tree-sitter/node-tree-sitter#190 and should only be merged along with it, with a proper strategy for how to update languages.

We need to consider how we are going to release such a thing as language authors will have to know to regenarate or modify those files...

[ObserverOfTime]

Rust and Python will also have breaking changes soon, so it's fine to break Node as well.
Keep in mind that you will have to rebase once #2438 is merged since it also edits the bindings.

One question: how would binding.cc look like for multi-language parsers (e.g. typescript)?

[segevfiner]

Just Object::New and do the same, and just set those objects on exports, instead of directly treating exports as a language. exports is just a plain object and is there for convenience and you can really return anything.

[amaanq]

thanks @segevfiner, I'll try and help out/review the PR in node-ts as well

[segevfiner]

Just note that as it stands this will only work with node-tree-sitter with that PR merged as there is no backwards or forwards compatibility in place. So be sure to merge it before releasing this.

[amaanq]

Yeah I know, we're not gonna have a release until then

[ObserverOfTime]

Just note that as it stands this will only work with node-tree-sitter with that PR merged as there is no backwards or forwards compatibility in place.

I did add forwards compatibility. The CLI will replace the old bindings with the new ones.

[segevfiner]

I mean for importing the grammars in the node bindings. The non-napi node bindings can't import napi grammars and vice versa.