Hi Jonas,
I'm not sure if there's a mistake with my email. I haven't received any
reply from other DDs yet, and there hasn't been any progress with the
package on mentor either.
I was wondering—do you have a maintenance solution that works for you? I
recently read up on the principles of treesitter again. Actually, the
dynamic library we need consists of C files generated by the grammar.js
file using treesitter-cli. If our vendor only provides a single js file
instead of a complete repository, it would help avoid the size concerns
you're worried about. We could integrate treesitter-cli into hx-grammar
and generate the C files during building. This way, we wouldn't need to
provide files that are not used in the grammar repository. Of course,
this solution only significantly reduces the lines of code that require
review; we might still need to review hundreds or even a thousand lines
of js code across dozens of repositories.
Best regards,
Junyong Liang
