@johnhenry/letterpress 0.2.1 → 0.2.2

package/.github/workflows/ci.yml

@@ -12,3 +12,6 @@ jobs:
       node-versions: '["26"]'
       os: '["ubuntu-latest"]'
       gate-commands: npm test
+
+  workflow-lint:
+    uses: johnhenry/workflows/.github/workflows/workflow-lint.yml@v1

package/.github/workflows/publish.yml

@@ -1,25 +1,22 @@
 name: Publish to npm
 
+# Publish model: main is the release branch. A push to main publishes only if
+# package.json's version isn't on npm yet (otherwise a clean no-op), then tags
+# v<version> and creates a GitHub Release. See johnhenry/workflows' README.
 on:
-  release:
-    types: [published]
   push:
-    # Redundant with the release trigger above -- see fileable's
-    # publish.yml / johnhenry/workflows' README for the full incident
-    # writeup: creating a release very soon after a push/merge to the
-    # same commit can silently drop the release event for a job whose
-    # body is uses: <external-repo>/...@v1. This gives a second,
-    # idempotency-safe chance to fire.
-    tags:
-      - "v*"
+    branches: [main]
   workflow_dispatch: {}
 
+concurrency:
+  group: publish-${{ github.ref }}
+  cancel-in-progress: false
+
 jobs:
   publish:
     permissions:
-      contents: read
-      id-token: write # required by the reusable workflow's provenance step --
-        # see johnhenry/workflows' README for why this must be declared here too.
+      contents: write # tag + GitHub Release by-product of npm-publish.yml
+      id-token: write # npm provenance
     uses: johnhenry/workflows/.github/workflows/npm-publish.yml@v1
     with:
       node-version: "26"

package/CHANGELOG.md

@@ -6,6 +6,16 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
 
 This project will adhere to [Semantic Versioning](https://semver.org/spec/v2.0.0.html) once it reaches 1.0.0.
 
+## [0.2.2] - 2026-10-14
+
+### Fixed
+
+- 🐛 **Multi-line bodies duplicated earlier lines** (#20). In
+  `utility/parse-http-text.mjs`, the line buffer was not cleared after each
+  committed body line, so a body of `a\nb\nc` came out as `a\nab\nabc`.
+  This affected `createResponse`/`createRoute`/`tagRequest`/`tagResponse`
+  (a regression since `0.2.0`; `0.0.3` was correct).
+
 ## [0.2.1] - 2026-10-01
 
 ### Fixed
@@ -117,7 +127,7 @@ already behaved) is the one `create-route.mjs` was always meant to have.
   carried over during the leroute -> `@johnhenry/letterpress` rename --
   it simply wasn't in the initial `@johnhenry/letterpress` source, a gap
   in that migration rather than an intentional removal. It was discovered
-  while porting a downstream consumer, `prism` (a live HTTP request
+  while porting a private downstream consumer (a live HTTP request
   inspector/proxy), whose proxy mode depends on it for rewriting proxied
   requests/responses. Ported unchanged in behavior as `rewrite.mjs`
   (`createRewriter`, plus `rewriteRequest`/`rewriteResponse`/`addRule`/
@@ -133,7 +143,7 @@ already behaved) is the one `create-route.mjs` was always meant to have.
 
 - ✨ **`router.mount(prefix, subHandler)`**: another `leroute` capability
   (`create-lerouter.mjs`'s `router.mount`) dropped during the same rename,
-  found via the same `prism` port -- prism's own top-level router uses it
+  found via the same port -- that app's own top-level router uses it
   to mount its dashboard sub-router under `/inspect`. Delegates every
   request under `prefix` to `subHandler` with the prefix stripped from the
   forwarded request's path; `subHandler` may be a plain `(Request) =>
@@ -155,9 +165,9 @@ already behaved) is the one `create-route.mjs` was always meant to have.
   and forwarded to `defaultHandler` too. This was also present in `leroute`
   (`router(request, ctx = {})`) and dropped during the rename; brought back
   specifically so `mount()` can hand a mounted sub-router its `mountPrefix`
-  (used by `prism` to reconstruct the full request path for display in its
+  (used by that app to reconstruct the full request path for display in its
   captured-request feed, purely cosmetic but a real fidelity gap otherwise)
-  -- caught by testing `mount()` end-to-end against `prism` itself, not by
+  -- caught by testing `mount()` end-to-end against that app itself, not by
   a direct comparison against the old source this time. Existing single-arg
   `router(request)` callers are unaffected (`ctx` defaults to `{}`).
 

package/README.md

@@ -265,7 +265,7 @@ rewriter.addRule({ match: { path: "/teapot" }, action: { setStatus: 418 } });
 > This existed in `leroute` (the package letterpress was renamed from --
 > see the provenance note near the top of this README) but was dropped
 > during that rename. It's ported here, discovered missing while porting a
-> downstream consumer (`prism`, a request inspector/proxy) that relies on
+> downstream consumer (a private request inspector/proxy) that relies on
 > it for proxy-mode rewriting -- see CHANGELOG.md.
 
 ### `deconstruct`, `cook`
@@ -318,13 +318,6 @@ is designed to pair with a sibling package that does.
   `Route`-shaped function works too; `leserve` is the tested, documented
   pairing, not a hard dependency (it's a `devDependency` here, used only in
   the demo scripts).
-- **[`@johnhenry/prism`](https://github.com/johnhenry/prism)** -- a live
-  HTTP request inspector/proxy that uses `createRouter()` as its top-level
-  router. Porting it surfaced two real gaps left over from letterpress's
-  own rename from `leroute`: `router.mount()` (with the `ctx`-forwarding
-  its `mountPrefix` depends on) and `createRewriter`
-  (`@johnhenry/letterpress/rewrite`) -- both closed as part of that port,
-  see CHANGELOG.md.
 
 ## 🤝 Contributing
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@johnhenry/letterpress",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "A tagged-template-string HTTP routing library for defining and matching request handlers with plain JavaScript syntax.",
   "main": "index.mjs",
   "types": "types.d.ts",

package/rewrite.mjs

@@ -8,7 +8,7 @@
  * see the README's provenance note) as `createRewriter`, but was dropped
  * during the leroute -> @johnhenry/letterpress rename. It's ported here
  * unchanged in behavior, discovered missing while porting a downstream
- * consumer (`prism`, a request inspector/proxy) that relies on it for
+ * consumer (a private request inspector/proxy) that relies on it for
  * proxy-mode rewriting.
  *
  * Rules format:

package/test/tag-req-res.mjs

@@ -1,6 +1,6 @@
 import { test } from "node:test";
 import { strict as assert } from "node:assert";
-import { tagRequest, tagResponse } from "../index.mjs";
+import { tagRequest, tagResponse, createResponse } from "../index.mjs";
 
 const createReadableStream = (data) =>
   new ReadableStream({
@@ -251,3 +251,34 @@ hello`;
     assert.equal(auto.headers.get("content-length"), "5");
   });
 });
+
+test("multi-line bodies are not duplicated (issue #20)", async (t) => {
+  await t.test("tagResponse", async () => {
+    const response = await tagResponse`HTTP/1.1 200 OK
+
+a
+b
+c`;
+    assert.equal(await response.text(), "a\nb\nc");
+  });
+
+  await t.test("tagRequest", async () => {
+    const request = await tagRequest()`POST /x HTTP/1.1
+
+a
+b
+c`;
+    assert.equal(await request.text(), "a\nb\nc");
+  });
+
+  await t.test("createResponse with substitution in a later line", async () => {
+    const name = "x";
+    const response = await createResponse`HTTP/1.1 200 OK
+Content-Type: text/plain
+
+line1
+line2 ${name}
+line3`;
+    assert.equal(await response.text(), "line1\nline2 x\nline3");
+  });
+});

package/utility/parse-http-text.mjs

@@ -142,6 +142,7 @@ export const parseHttpText = async (strings, substitutions, options = {}) => {
       if (p > 0) {
         if (zone === "body") {
           commitBodyLine(lineBuffer, false);
+          lineBuffer = "";
         } else {
           flushLine();
         }