tree-sitter-hujson 0.2.3

Hujson grammar for tree-sitter

tree-sitter-hujson

A tree-sitter grammar for HuJSON (Human JSON) — also known as JWCC (JSON With Commas and Comments).

HuJSON is a strict superset of JSON that adds exactly two features:

• C-style comments — line comments (//) and block comments (/* */)
• Trailing commas — optional trailing comma after the last element in arrays and objects

All valid JSON is valid HuJSON. HuJSON intentionally rejects all other extensions (unquoted keys, hex literals, Infinity/NaN, single-quoted strings, etc.).

The grammar registers both the .hujson and .jwcc file extensions.

Provenance

Forked from tree-sitter/tree-sitter-json at commit 001c28d.

The only semantic change is the commaSep helper, which now allows an optional trailing comma:

function commaSep1(rule) {
  return seq(rule, repeat(seq(',', rule)), optional(','));
}

The upstream grammar already supported comments, so no further changes were needed.

Consumers

• Zed — via the ggfevans/zed-hujson extension
• Neovim / Helix — usable directly via the standard tree-sitter grammar interface

Development

Prerequisites

• Node.js 18+
• tree-sitter-cli (npm install -g tree-sitter-cli)

Build & test

tree-sitter generate
tree-sitter test

The corpus suite covers literals, objects, arrays, comments, trailing commas, degenerate inputs (empty/whitespace/BOM/unicode/deeply nested), and invalid inputs (the strictness-preserving rejections).

Releasing

Releases are tag-driven. Bump the version in every manifest at once with scripts/bump-version.sh X.Y.Z, add a matching ## [X.Y.Z] entry to CHANGELOG.md, then push a vX.Y.Z tag. The Release workflow creates the GitHub Release and publishes the bindings.

Registry publishing degrades gracefully — each publish job runs only when its credential is configured, otherwise it is skipped (the GitHub Release always succeeds):

Registry	Enable by configuring
npm	repo secret NPM_TOKEN
crates.io	repo secret CARGO_REGISTRY_TOKEN
PyPI	repo variable PYPI_TRUSTED_PUBLISHER = true (after setting up a PyPI trusted publisher for this repo + release.yml; uses OIDC, no token)

To publish a registry you enabled after a tag was already cut, re-run the Release workflow for that tag — the now-present credential flips its job on.

Licence

MIT — matches the upstream tree-sitter-json licence.