ObserverOfTime
ObserverOfTime
> The [workflows](https://github.com/tree-sitter/workflows/blob/main/.github/workflows/package-npm.yml) are not generated by default by generate so how are language authors supposed to know about them? The workflows are still subject to change but a reference...
Rust and Python will also have breaking changes soon, so it's fine to break Node as well. Keep in mind that you will have to rebase once #2438 is merged...
> Just note that as it stands this will only work with node-tree-sitter with that PR merged as there is no backwards or forwards compatibility in place. I did add...
Closing as duplicate of #608. (PR very welcome.)
The build is going to be handled by the parser soon but we could add a CLI for parsing and querying.
The playground is outdated. This happens because the parser considers [match](https://docs.python.org/3/reference/compound_stmts.html#match) a statement.
I think `has*` (maybe `is*` as well?) make more sense as functions. > I could understand things that require traversing the tree being functions though. This too.
This has been resolved.
It should be documented that using a parser in your project can be tricky. You have to add the parser as a submodule and have these in `go.mod`: ``` require...
Can this be merged now that #84 resolved the `proc.spawn` thing?