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?