@fluixi/template-parser 0.1.0-alpha.3 → 1.0.0-alpha.100

package/dist/index.d.cts

@@ -0,0 +1,31 @@
+/**
+ * @fluixi/template-parser: the dependency-free foundation for every tool that
+ * needs to understand a Fluixi `` html`...` `` template: the compiler, the
+ * language server, the TypeScript plugin, and the Biome/formatter plugin.
+ *
+ * Pipeline:  pieces → {@link Reader} (lexing/holes) → {@link parseTemplate}
+ * (structure + diagnostics) → Template AST. Downstream, each tool binds the
+ * opaque hole slots to its own representation and consumes the AST, the
+ * compiler lowers it to codegen IR, the LSP answers completion/hover/rename.
+ *
+ * The parser never resolves the JS inside `${…}`; it records each hole as an
+ * index + span. That is the single seam that keeps this package host-agnostic.
+ */
+export * from './ast.cjs';
+export { Reader, type Piece, type HoleToken } from './reader.cjs';
+export { CORE_DIRECTIVES, resolveAttribute, type DirectiveDescriptor, type RawAttribute, } from './directives.cjs';
+export { parseTemplate, type ParserOptions } from './parser.cjs';
+import type { Piece } from './reader.cjs';
+import { type ParserOptions } from './parser.cjs';
+import type { ParseResult, SourceSpan } from './ast.cjs';
+/**
+ * Build a piece list from the static string segments of a tagged template
+ * (`quasi.strings`), inserting a hole between each pair. Offsets are synthetic
+ * (cumulative over the joined text), good enough for standalone parsing and
+ * tests. Hosts with real source positions (the compiler, the LSP) should build
+ * {@link Piece}s directly so spans map back to the original file.
+ */
+export declare function piecesFromStrings(statics: readonly string[]): Piece[];
+/** Convenience: parse directly from static string segments. */
+export declare function parse(statics: readonly string[], opts?: ParserOptions): ParseResult;
+export type { SourceSpan };

package/dist/index.d.ts

@@ -1,11 +1,11 @@
 /**
- * @fluixi/template-parser — the dependency-free foundation for every tool that
+ * @fluixi/template-parser: the dependency-free foundation for every tool that
  * needs to understand a Fluixi `` html`...` `` template: the compiler, the
  * language server, the TypeScript plugin, and the Biome/formatter plugin.
  *
  * Pipeline:  pieces → {@link Reader} (lexing/holes) → {@link parseTemplate}
  * (structure + diagnostics) → Template AST. Downstream, each tool binds the
- * opaque hole slots to its own representation and consumes the AST — the
+ * opaque hole slots to its own representation and consumes the AST, the
  * compiler lowers it to codegen IR, the LSP answers completion/hover/rename.
  *
  * The parser never resolves the JS inside `${…}`; it records each hole as an
@@ -21,7 +21,7 @@ import type { ParseResult, SourceSpan } from './ast.js';
 /**
  * Build a piece list from the static string segments of a tagged template
  * (`quasi.strings`), inserting a hole between each pair. Offsets are synthetic
- * (cumulative over the joined text) — good enough for standalone parsing and
+ * (cumulative over the joined text), good enough for standalone parsing and
  * tests. Hosts with real source positions (the compiler, the LSP) should build
  * {@link Piece}s directly so spans map back to the original file.
  */

package/dist/index.js

@@ -1,11 +1,11 @@
 /**
- * @fluixi/template-parser — the dependency-free foundation for every tool that
+ * @fluixi/template-parser: the dependency-free foundation for every tool that
  * needs to understand a Fluixi `` html`...` `` template: the compiler, the
  * language server, the TypeScript plugin, and the Biome/formatter plugin.
  *
  * Pipeline:  pieces → {@link Reader} (lexing/holes) → {@link parseTemplate}
  * (structure + diagnostics) → Template AST. Downstream, each tool binds the
- * opaque hole slots to its own representation and consumes the AST — the
+ * opaque hole slots to its own representation and consumes the AST, the
  * compiler lowers it to codegen IR, the LSP answers completion/hover/rename.
  *
  * The parser never resolves the JS inside `${…}`; it records each hole as an
@@ -19,7 +19,7 @@ import { parseTemplate } from './parser.js';
 /**
  * Build a piece list from the static string segments of a tagged template
  * (`quasi.strings`), inserting a hole between each pair. Offsets are synthetic
- * (cumulative over the joined text) — good enough for standalone parsing and
+ * (cumulative over the joined text), good enough for standalone parsing and
  * tests. Hosts with real source positions (the compiler, the LSP) should build
  * {@link Piece}s directly so spans map back to the original file.
  */