npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

sqs-partial-batch-processor

v0.4.3

Published

A small TypeScript helper for AWS Lambda SQS triggers using partial batch responses (SQSBatchResponse.batchItemFailures). You supply per-record async logic; the library handles looping, per-record error boundaries, and the response shape.

Readme

SQS Partial Batch Processor

npm build

A small TypeScript helper for AWS Lambda SQS triggers using partial batch responses (SQSBatchResponse.batchItemFailures). You supply per-record async logic; the library handles looping, per-record error boundaries, and the response shape.

This library intentionally does not parse message bodies, validate schemas, create AWS SDK clients, or make retry/business decisions for you.

Import the public API from the package root (processPartialBatch, processPartialBatchWithResult, ProcessPartialBatchOptions, ProcessRecordResult).

Features

  • Implements Lambda SQS partial batch response pattern (only failed messages are retried).
  • Per-record error boundary (failures are isolated to each record).
  • Aggregates failed identifiers into batchItemFailures (defaults to messageId).
  • Throw-style (processPartialBatch) and Result-style (processPartialBatchWithResult) APIs.
  • Typed Result callback via ProcessRecordResult ({ ok: true } | { ok: false }).
  • Optional bounded concurrency (concurrency), error hook (onRecordError), and custom itemIdentifier mapping (mapMessageId).
  • Shared options type ProcessPartialBatchOptions for both APIs.
  • For { ok: false }, onRecordError receives an Error that includes the resolved itemIdentifier (message and cause) for easier debugging.

Requirements

  • Node.js 20+ (runtime requirement)
  • Module system: published as CommonJS ("main": "lib/index.js"). Usable from both CJS and ESM runtimes.
  • Lambda SQS event source mapping has Report batch item failures enabled. See: AWS Lambda SQS error handling docs

Installation

npm install sqs-partial-batch-processor
yarn add sqs-partial-batch-processor
pnpm add sqs-partial-batch-processor

Usage

Throw to mark a record as failed:

import type { SQSEvent } from 'aws-lambda';
import { processPartialBatch } from 'sqs-partial-batch-processor';

export const handler = async (event: SQSEvent) =>
  processPartialBatch(event, async (record) => {
    // Your per-record logic here.
    // Throw to mark only this record's messageId as failed.
  });

Result-style callback (no throw for control flow). Return a ProcessRecordResult:

  • { ok: true }: success (not listed in batchItemFailures)
  • { ok: false }: failure (listed in batchItemFailures)
  • thrown errors: still treated as failures
import type { SQSEvent } from 'aws-lambda';
import {
  processPartialBatchWithResult,
  type ProcessRecordResult,
} from 'sqs-partial-batch-processor';

export const handler = async (event: SQSEvent) =>
  processPartialBatchWithResult(event, async (record): Promise<ProcessRecordResult> => {
    if (record.body === '') {
      return { ok: false };
    }
    return { ok: true };
  });

Options

Both processPartialBatch and processPartialBatchWithResult accept an optional ProcessPartialBatchOptions object:

  • concurrency?: number (default: 1): maximum parallelism. Must be a finite integer >= 1 (1 = sequential, > 1 = bounded concurrency). If invalid, the function throws (RangeError for < 1, TypeError for non-integer / non-finite).
    • Tip: start with 1 and increase gradually while watching downstream limits (external API rate limits, DB connection pools, and Lambda reserved concurrency). SQS batches are typically small, so a large value rarely helps.
    • Note: when concurrency > 1, the order of batchItemFailures is not guaranteed. Tests should compare as a set, not by array order.
  • onRecordError?: (record, error) => void: called when a record is treated as failed (useful for structured logs / metrics).
    • Caution: do not log record.body as-is in onRecordError. Message bodies often contain secrets or personal data. Prefer messageId / your mapMessageId result and a sanitized error summary.
    • When processPartialBatchWithResult receives { ok: false }, the hook gets an Error whose message (and cause.itemIdentifier) includes the resolved itemIdentifier for easier debugging.
    • Example (structured log / metrics hook):
import type { SQSEvent } from 'aws-lambda';
import { processPartialBatch } from 'sqs-partial-batch-processor';

export const handler = async (event: SQSEvent) =>
  processPartialBatch(
    event,
    async (record) => {
      // ...
    },
    {
      onRecordError: (record, error) => {
        console.log(JSON.stringify({
          level: 'error',
          msg: 'record failed',
          messageId: record.messageId,
          // Do not log record.body — it may contain secrets or PII.
          error: error instanceof Error ? { name: error.name, message: error.message } : { message: String(error) },
        }));
      },
    },
  );
  • mapMessageId?: (record) => string: customize the itemIdentifier (defaults to record.messageId).
    • Typical uses: align the identifier with an application-level id (e.g., an id stored in messageAttributes or the parsed payload), or normalize identifiers across FIFO/standard queues for easier correlation.

License

This project is licensed under the Apache-2.0 License.