@oh-my-pi/pi-utils 14.3.0 → 14.4.0

package/package.json

@@ -1,7 +1,7 @@
 {
 	"type": "module",
 	"name": "@oh-my-pi/pi-utils",
-	"version": "14.3.0",
+	"version": "14.4.0",
 	"description": "Shared utilities for pi packages",
 	"homepage": "https://github.com/can1357/oh-my-pi",
 	"author": "Can Boluk",
@@ -38,7 +38,7 @@
 	},
 	"devDependencies": {
 		"@types/bun": "^1.3.13",
-		"@oh-my-pi/pi-natives": "14.3.0"
+		"@oh-my-pi/pi-natives": "14.4.0"
 	},
 	"engines": {
 		"bun": ">=1.3.7"

package/src/prompt.ts

@@ -402,8 +402,24 @@ export function registerPartial(name: string, fn: Template): void {
 	handlebars.registerPartial(name, fn);
 }
 
+/**
+ * Handlebars' lexer greedily matches `}}}` as `CLOSE_UNESCAPED` (the close of a
+ * triple-stash `{{{ ... }}}`). When a regular helper close `}}` is immediately
+ * followed by a literal `}` (common in compact JSON examples like
+ * `{del:{{href ...}}}`), the lexer mistakes the trailing `}}}` for a triple-close
+ * and rejects the input.
+ *
+ * We never use triple-stash (it's redundant under `noEscape: true`), so any run
+ * of 3+ closing braces is unambiguously "helper close `}}`" + "literal `}`s".
+ * Inject a no-op comment between them so the lexer tokenizes the helper close
+ * cleanly and treats the rest as content.
+ */
+function disambiguateClosingBraces(template: string): string {
+	return template.replace(/\}\}(\}+)/g, "}}{{!---}}$1");
+}
+
 export function compile(template: string): (context: TemplateContext) => string {
-	return handlebars.compile(template, { noEscape: true, strict: false });
+	return handlebars.compile(disambiguateClosingBraces(template), { noEscape: true, strict: false });
 }
 
 export function render(template: string, context: TemplateContext = {}): string {