@willbooster/tree-sitter-html 1.0.4 → 1.0.5

package/README.md

@@ -19,7 +19,8 @@ number, so it loads only with the WillBooster runtime, version 2.0.0 or later
 [@willbooster/web-tree-sitter](https://www.npmjs.com/package/@willbooster/web-tree-sitter)); upstream's runtime rejects
 it. Input that contains NUL characters can parse to a different tree than with upstream's 0.23.2 parser, because the
 lexers that generator emits treat a NUL character as an ordinary character. This grammar also accepts literal `>`
-characters in text nodes, which upstream 0.23.2 rejects. Its scanner requires an HTML tag-name boundary after
+characters and bare `&` in text nodes, which upstream 0.23.2 rejects. A bare `&` becomes its own `text` node beside
+surrounding text, while character references remain `entity` nodes. Its scanner requires an HTML tag-name boundary after
 `</script` and `</style`, so longer names and overlapping prefixes remain raw text. Closing-name comparisons
 fold only ASCII letters, and embedded NUL characters remain part of raw-text content. Void elements close
 before following text, entities, and complete comments, which become siblings instead of children.

package/grammar.js

@@ -134,6 +134,6 @@ module.exports = grammar({
       seq('"', optional(alias(/[^"]+/, $.attribute_value)), '"'),
     ),
 
-    text: _ => /[^<&\s]([^<&]*[^<&\s])?/,
+    text: _ => /[^<&\s]([^<&]*[^<&\s])?|&/,
   },
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@willbooster/tree-sitter-html",
-  "version": "1.0.4",
+  "version": "1.0.5",
   "description": "HTML grammar for tree-sitter",
   "keywords": [
     "incremental",

package/tree-sitter.json

@@ -18,7 +18,7 @@
     }
   ],
   "metadata": {
-    "version": "1.0.4",
+    "version": "1.0.5",
     "license": "MIT",
     "description": "HTML grammar for tree-sitter",
     "authors": [