publish to npm?

[janw4ld]

official treesitter grammars are all published to npm, example, and some projects that depend on tree-sitter use the npm registry as the only option to fetch and manage versions of a grammar, so it would be great if we managed an npm package for this repo. i can see that the unscoped tree-sitter-groovy name is already taken tho.

[murtaza64]

I wouldn't be opposed to setting this up, but I've never published a package on npm. @amaanq thoughts on how to resolve the name collision?

[amaanq]

you can use a scope

[murtaza64]

since this parser is used upstream in nvim-treesitter, would you be willing to scope yours and let this project take the unqualified name?

[thoroc]

Sorry to jump on this open issue, but until this is published to the npm registry, how do you go about exporting this to use in a node project?

[janw4ld]

@thoroc you can use npm i https://github.com/murtaza64/tree-sitter-groovy to install it directly from github.

[thoroc]

@janw4ld Thank you for your answer.

I am experimenting with Deno and that doesn't seem to be working out of the box. I've got a bit further with the help of a couple of tools though:

• https://deno.land/x/binaryify@2.5.3.0
• https://deno.land/x/deno_tree_sitter@0.2.8.4