This is more a question than anything.
I can see that last published npm version of tree-sitter is [email protected]. After that releases stopped. Tree-sitter github repo is currently at v0.16.9.
tree-sitter-cli seems to be reflecting the tree-sitter github releases and is currently at 0.16.9 version which is the same as last GitHub release.
web-tree-sitter is at version 0.16.4.
I suppose that those npm package versions reflect the Github releases of tree-sitter and ideally their version should be same for all the packages when used inside one project. Would it be possibly to release latest version of tree-sitter, tree-sitter-cli and web-tree-sitter packages?
Thanks you
Issue-Label Bot is automatically applying the label question to this issue, with a confidence of 0.62. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
We already to publish everything to npm. There are three modules on npm:
tree-sitter-cli - the command line tool, implemented in the cli directory of this repoweb-tree-sitter - the WASM binding - implemented in the lib/binding_web directory of this repotree-sitter - The original Node.js binding using native extension - implemented in the node-tree-sitter repoThey generally are going to have different versions, because they are different code. But we do generally keep their minor version numbers (and the minor version numbers of the generated parsers) in sync.
@maxbrunsfeld thanks for releasing npm packages and additional explanation about them.
Most helpful comment
Issue-Label Bot is automatically applying the label
questionto this issue, with a confidence of 0.62. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!Links: app homepage, dashboard and code for this bot.