How to add custom treesitter grammars locally?

[treeman]

I've got a bunch of scrappy ad-hoc treesitter grammars I use that I don't want to upstream. Would it be possible to render these extra grammars via arborium too?

I tried to keep the pipelines completely separate but it seems I can't have both tree-sitter and arborium as dependencies:

package `tree-sitter` links to the native library `tree-sitter`, but it conflicts with a previous package which links to `tree-sitter` as well:
package `arborium-tree-sitter v2.3.0`
    ... which satisfies dependency `arborium-tree-sitter = "^2.3.0"` of package `arborium v2.3.0`
    ... which satisfies dependency `arborium = "^2.3.0"` of package `jonashietala_se v0.1.0 (/home/tree/code/jonashietala)`
Only one package in the dependency graph may specify the same links value. This helps ensure that only one copy of a native library is linked in the final binary. Try to adjust your dependencies so that only one package uses the `links = "tree-sitter"` value. For more information, see https://doc.rust-lang.org/cargo/reference/resolver.html#links.

Some advice/documentation here would be great.

I'm personally not interested in the WASM capabilities and only want to render it natively via Rust.

[ssokolow]

While I don't currently have my own tree-sitter setup, I would like to know what my options are for situations like "I don't think it'd be fair to ask arborium to support every niche retro-hobby syntax under the sun".

(eg. I could see myself using a bunch of crates like tree-sitter-pascal, tree-sitter-applesoft, tree-sitter-integerbasic, and whatever else people whip up in the blog generator I'm working on. I'm perfectionist enough about output that I've already got latex2mathml hooked up as a JS-free way to render the Markdown math extension and whipped up shortcodes for in-paragraph visualizations of basically every gamepad button for every major game console of the last 40 years, as well as keyboard keys with included symbols like ⌘, ⌥, and ⌤.)

[fasterthanlime]

but it seems I can't have both tree-sitter and arborium as dependencies:

that is correct. arborium has its own tree-sitter fork. and it is mostly for wasm reasons indeed.

So the challenge here is that most of the work for the grammars that are in the monorepo is done by the cargo-xtask. And there's a bunch of automated stuff that would be very annoying to do manually, so I guess the actionable part of this issue is to extract that into a tool that you can run locally?

---

I could see myself using a bunch of crates like tree-sitter-pascal, tree-sitter-applesoft, tree-sitter-integerbasic

All three of those I would be happy to upstream by the way!