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

@shipbook/node

v1.1.1

Published

Shipbook SDK for Node.js - Remote logging and error tracking for servers and serverless

Readme

@shipbook/node

Shipbook SDK for Node.js applications. Capture logs, errors, and exceptions from your server-side applications, APIs, and serverless functions, and view them in the Shipbook console.

Installation

npm install @shipbook/node

Quick Start

import Shipbook from '@shipbook/node';

// Initialize Shipbook (do this once at app startup)
await Shipbook.start('YOUR_APP_ID', 'YOUR_APP_KEY');

// Get a logger for your module
const log = Shipbook.getLogger('MyService');

// Log messages at different severity levels
log.verbose('Detailed trace information');
log.debug('Debug information');
log.info('General information');
log.warning('Warning message');
log.error('Error message');

// Log with additional parameters (like console.log)
log.debug('Request data:', { method: 'POST', path: '/api' });
log.info('Processing items:', ['item1', 'item2']);
log.debug('User:', userId, 'Action:', action);

// Log with an error object (must be last argument)
try {
  await someOperation();
} catch (error) {
  log.error('Operation failed', error);
  log.error('Failed with context:', { requestId }, error);
}

Features

  • Remote Logging - View all your server logs in the Shipbook console
  • Error Tracking - Automatically captures uncaught exceptions and unhandled rejections
  • Session Tracking - Group logs by request/session
  • Persistent Storage - Logs are stored locally and sent when connectivity is available
  • Dynamic Configuration - Change log levels remotely without redeploying
  • User Identification - Associate logs with specific users or requests

Configuration

Enable Inner Logging (Debug Mode)

Shipbook.enableInnerLog(true);

Register User/Request Context

Shipbook.registerUser(
  'user-123',           // userId
  '[email protected]',   // email (optional)
  'John Doe',           // userName (optional)
  'John',               // firstName (optional)
  'Doe',                // lastName (optional)
  { role: 'admin' }     // additionalInfo (optional)
);

Framework Integration

Express

import express from 'express';
import Shipbook from '@shipbook/node';

const app = express();
const log = Shipbook.getLogger('ExpressApp');

// Initialize before starting server
Shipbook.start('YOUR_APP_ID', 'YOUR_APP_KEY').then(() => {
  app.listen(3000, () => {
    log.info('Server started on port 3000');
  });
});

app.get('/', (req, res) => {
  log.info('Request received', { path: req.path });
  res.send('Hello World');
});

NestJS

// main.ts
import Shipbook from '@shipbook/node';

async function bootstrap() {
  await Shipbook.start('YOUR_APP_ID', 'YOUR_APP_KEY');
  
  const app = await NestFactory.create(AppModule);
  await app.listen(3000);
}
bootstrap();

AWS Lambda / Serverless

import Shipbook from '@shipbook/node';

const log = Shipbook.getLogger('LambdaHandler');

// Initialize outside handler for connection reuse
const initPromise = Shipbook.start('YOUR_APP_ID', 'YOUR_APP_KEY');

export const handler = async (event: any) => {
  await initPromise;
  
  log.info('Lambda invoked', { event });
  
  // Your handler logic
  return { statusCode: 200, body: 'Success' };
};

Background Jobs

Use runInContext to group logs from background jobs into separate sessions. Each job run gets a unique session ID.

import Shipbook from '@shipbook/node';

// Process email queue with its own session
await Shipbook.runInContext({ jobName: 'email-queue' }, async () => {
  const log = Shipbook.getLogger('EmailProcessor');

  log.info('Processing email queue');
  // ... process emails ...
  log.info('Email queue completed', { processed: 100 });
});

// Data cleanup job with custom metadata
await Shipbook.runInContext(
  { jobName: 'data-cleanup', metadata: { priority: 'low' } },
  async () => {
    const log = Shipbook.getLogger('DataCleanup');

    log.info('Starting cleanup');
    // ... cleanup logic ...
    log.info('Cleanup completed');
  }
);

Each runInContext call creates a unique session, with the job name stored in the session metadata for filtering in the Shipbook console.

Storage Location

Logs are persisted to ~/.shipbook/ by default. This ensures logs are not lost if the process crashes or loses connectivity.

Getting Your App ID and Key

  1. Sign up at shipbook.io
  2. Create a new application in the console
  3. Copy your App ID and App Key from the application settings

Requirements

  • Node.js 14.0.0 or higher

Links

License

MIT