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

@quaillogistics/adapters

v0.2.1

Published

TMS adapter library — fetch and map data from 3PL Systems, Turvo, and other TMS platforms

Readme

@quaillogistics/adapters

TMS adapter library for fetching and mapping data from external TMS systems. Used internally by QUAIL Logistics.

Install

npm install @quaillogistics/adapters

Usage

Each TMS adapter is a separate subpath export. Import only what you need:

import { ThreePLClient, mapThreePLLoad } from '@quaillogistics/adapters/3pl'
import { TurvoClient } from '@quaillogistics/adapters/turvo'
import { chunkDateRange } from '@quaillogistics/adapters/common'

3PL Systems

const client = new ThreePLClient({
  apiHost: '3pl.hyperiontms.com',
  clientId: '...',
  clientSecret: '...',
  globalClientId: '...',
  globalClientSecret: '...',
})

// Layer 1: typed raw API responses
const rawLoads = await client.getLoads({ startDate, endDate })

// Layer 2: opt-in mapped intermediaries
const loads = rawLoads.map(mapThreePLLoad)

Turvo

const client = new TurvoClient({
  apiHost: 'app.turvo.com',
  username: '...',
  password: '...',
  apiKey: '...',
  clientId: '...',
  clientSecret: '...',
})

const shipment = await client.getShipment(123)

Mock mode

Every adapter supports mock: true for testing without hitting real APIs:

const client = new ThreePLClient({
  ...credentials,
  mock: true,
})

const loads = await client.getLoads({ startDate, endDate }) // deterministic test data

Observability

Pass logging callbacks to see HTTP activity:

const client = new ThreePLClient({
  ...credentials,
  onRequest: (method, path) => console.log(`>> ${method} ${path}`),
  onResponse: (method, path, status, ms) => console.log(`<< ${status} ${path} (${ms}ms)`),
})

Adapters

| Adapter | Import | Capabilities | |---------|--------|-------------| | 3PL Systems | @quaillogistics/adapters/3pl | Pull: loads, carriers, customers, contacts, commissions, AP invoices, vendor payments, tracking, documents | | Turvo | @quaillogistics/adapters/turvo | Push: shipment CRUD. Read: shipments, locations |

Development

npm install
npm run test        # run tests
npm run test:watch  # watch mode
npm run typecheck   # type check
npm run build       # build to dist/
npm run check-deps  # verify zero production dependencies

Publishing

  1. Bump version in package.json
  2. Commit: git commit -m "v0.1.0"
  3. Tag: git tag v0.1.0
  4. Push: git push && git push --tags

CI will run checks and publish to npm automatically.