per-lang packages about tree-sitter-wasms HOT 5 OPEN

IMO, people using this package are on the I want it all camp.

from tree-sitter-wasms.

1. Could this be the reason why I've been seeing test failures on some of my tree sitter queries (they ran ok earlier)? Does that mean we should be using "web-tree-sitter" v 0.20.8 as well (same version as tree-sitter-cli)?

Interesting! It could very well be, especially if they work in the playground (if your lang is included there).

Would publishing the individual wasms separately also require us to use different versions of "web-tree-sitter" for each grammar?

Good point, I blindly assumed there wouldn't be breaking changes, but reading this and other threads makes me think that was wildly naive. So I guess yes, the best idea for now would be to keep the web-tree-sitter version used in sync with tree-sitter-cli.
I'll make sure to denote it in the README.

Thanks for all the comments so far, I'll stick with all-inclusive then and will update tree-sitter-cli on a lowest-common-denominator basis. Maybe I'll even keep the versioning scheme synced with tree-sitter itself?!

from tree-sitter-wasms.

Hi @Gregoor,

1. Could this be the reason why I've been seeing test failures on some of my tree sitter queries (they ran ok earlier)? Does that mean we should be using "web-tree-sitter" v 0.20.8 as well (same version as tree-sitter-cli)?

Would publishing the individual wasms separately also require us to use different versions of "web-tree-sitter" for each grammar?

2. is not an issue at the moment. I'm trying to provide multiple language support to a VS Code extension (Continue), so need to select parser based on file extension being used.

from tree-sitter-wasms.

FWIW: I'm also in the "I want it all" camp.

from tree-sitter-wasms.

IMO, people using this package are on the I want it all camp.

I agree on this

from tree-sitter-wasms.