Publish on npm

[rien]

This grammar is not published on npm, although it is properly working (when #40 is merged).

Can this grammar be published there?

[kevinushey]

It could, but I'd like to wait until https://github.com/r-lib/tree-sitter-r/tree/next is merged -- I'm working on a fairly substantial overhaul of the grammar.

[rien]

@kevinushey in what timeframe do you expect this could be possible?

For our purposes, the current version is very usable and having a big change in the grammar in a later release would not be a problem.

[kevinushey]

I think we've decided to maintain "main" and "next" separately, just because it would be too costly to try to bring any existing downstream integrations (e.g. in vim / neovim / Emacs) up to speed.

Still, we don't have a timeline for publishing to NPM just yet.

[rien]

For our case there is no need anymore for this to be published, we've decided to vendor the parsers we're using.

[kevinushey]

Makes sense; thanks!

[EagleoutIce]

Now, that the branch in question is long merged, do you intend on doing this now? @kevinushey.

[kevinushey]

@DavisVaughan, what do you think?

[DavisVaughan]

Since we are on main now, and since we publish Rust and R bindings, it probably makes sense to also publish npm bindings too (that's probably the other major consumer of tree-sitter these days, especially with wasm support). I'll look into that for the next release.

[EagleoutIce]

Thank you very much this would help us greatly!