| Crates.io | arborium-vue |
| lib.rs | arborium-vue |
| version | 2.12.4 |
| created_at | 2025-12-04 22:30:21.69357+00 |
| updated_at | 2026-01-18 11:10:39.840921+00 |
| description | Vue grammar for arborium (tree-sitter bindings) |
| homepage | https://github.com/bearcove/arborium |
| repository | https://github.com/bearcove/arborium |
| max_upload_size | |
| id | 1967227 |
| size | 224,392 |
Vue grammar for tree-sitter.
Progressive JavaScript framework for UIs; official docs at vuejs.org.
| Inventor | Evan You |
| Year | 2014 |
use arborium_vue::language;
use tree_sitter_patched_arborium::Parser;
let mut parser = Parser::new();
parser.set_language(&language()).expect("Error loading vue grammar");
let source_code = "/* your vue code here */";
let tree = parser.parse(source_code, None).unwrap();
println!("{}", tree.root_node().to_sexp());
For most use cases, prefer the main arborium crate:
[dependencies]
arborium = { version = "*", features = ["vue"] }
Or use this crate directly:
[dependencies]
arborium-vue = "*"
This crate is part of Arborium, a collection of tree-sitter grammars packaged as Rust crates, maintained by Amos Wenger.
This crate packages a parser.c file generated by the tree-sitter CLI. It exports a language() function returning the tree-sitter Language for vue.
Why separate crates? Tree-sitter parsers can be large (some exceed 1MB of generated C). Splitting languages into separate crates means you only compile what you need, and parallel/incremental builds are more effective.
cc cratewasm32-unknown-unknown (with custom sysroot)| Repository | tree-sitter-grammars/tree-sitter-vue |
| Commit | 22bdfa6c9fc0f5ffa44c6e938ec46869ac8a99ff |
| License | MIT |
To regenerate after upstream updates:
cargo xtask gen --name vue
Found a grammar bug? Please report it to the upstream repository.
This crate uses unsafe for FFI bindings to the tree-sitter C library. The unsafe surface is minimal and limited to what tree-sitter requires. The generated parser code is produced by tree-sitter's own code generator.
Crate versions track Arborium releases, not upstream grammar versions. The upstream commit is recorded above. A major version bump occurs when grammar changes affect node names or structure (breaking for query consumers).
parser.c): MIT (from upstream grammar)