Closed maxbrunsfeld closed 5 years ago
it's an optional convenience
Is the alternative running compliation commands manually? Or is there some other (more modern; less deprecated) workflow that can be automated?
Well, installing node-gyp
explicitly is optional, since it's bundled as part of npm
. I guess I was trying to include only the minimal dependencies.
But on second thought, that's probably not a worthwhile concern. This whole CLI is only installed by people who are developing parsers, so it probably just makes sense to add an explicit dependency on node-gyp
, for everyone's convenience.
Fixes https://github.com/tree-sitter/tree-sitter-cli/issues/43
This PR adds a
tree-sitter build
subcommand. It behaves liketree-sitter generate && node-gyp build
. It will also runnode-gyp configure
if you have not built yet.I haven't added
node-gyp
as an actual dependency for now, since it's an optional convenience. I just added an error message that suggests installing it if you try to runtree-sitter build
without it./cc @superlou @Aerijo