tree-sitter-javascript-orchard
This is a tree-sitter grammar for JavaScript.
Using it
You can obtain this parser in various formats:
- as an archive from the Releases page, which contains all the generated files (bindings, parser code)
- as a Rust crate:
cargo add tree-sitter-javascript-orchard - as a Python package:
pip install tree-sitter-javascript-orchard - as an NPM package:
npm install tree-sitter-javascript-orchard - As a Git repository with check-in generated files, via the GitHub mirror
Contributing
Contributions are welcome, so are co-maintainers.
Unlike many grammar repositories, this one does not track generated files.
After cloning this repository, you'll need to run tree-sitter generate to obtain the parser.
If you want to use it via bindings, you'll also need to run tree-sitter init.
Origin
This project was forked from https://github.com/tree-sitter/tree-sitter-javascript, to ease the use of and collaboration on this grammar.
1 maintainer
Metadata
1 maintainer
Release files for tree-sitter-javascript-orchard 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tree_sitter_javascript_orchard-0.2.0.tar.gz | 153.4 kB | Without provenance | Details for tree_sitter_javascript_orchard-0.2.0.tar.gz |
Release files / tree_sitter_javascript_orchard-0.2.0.tar.gz
| Download URL | tree_sitter_javascript_orchard-0.2.0.tar.gz |
|---|---|
| Size | 153.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
258f57df05081c94c020b61564a661de944e052917bdc02c4ab5102eb1e82ba5
|
|
BLAKE2b-256 checksum How to use checksums |
67db0d1e0c27e45ef8f96c82dcb0f29413670ce6bdd472872283b53ec4c4b943
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for tree-sitter-javascript-orchard 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
