Mirrored from nix-community#66 by @jeff-hykin (opened 2024-08-02T13:11:50Z).
This issue is tracked here so the fork can work on it; upstream may not respond. Please add new context in this issue.
I'd like to use the wasm version of this (client side in a browser) to highlight code.
I can build the wasm myself (and I do) but my version is effectively always out of date. I'd really appreciate it if there were releases of the wasm builds that I could easily pull.
A versioning scheme for releases was discussed:
If we started cutting releases the wasm grammar could be uploaded to the github releases API.
To do that we'd have to figure out a version number scheme. I'd suggest something like:
${tree-sitter.major}.${tree-sitter.minor}.${patch}major.minor would indicate tree-sitter compatibility & patch would be an incrementing counter indicating the release of tree-sitter-nix.
that would work perfectly for me and (as someone who maintains a tree sitter library API) I greatly appreciate the versioning being tied to the tree sitter version.
I'd like to use the wasm version of this (client side in a browser) to highlight code.
I can build the wasm myself (and I do) but my version is effectively always out of date. I'd really appreciate it if there were releases of the wasm builds that I could easily pull.
A versioning scheme for releases was discussed:
that would work perfectly for me and (as someone who maintains a tree sitter library API) I greatly appreciate the versioning being tied to the tree sitter version.