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

nested-group-by-ts

v0.0.7

Published

Structures a flat 2D array of relational data into a hierarchical structure

Readme

nested-group-by-ts 🪆

Structures a flat 2D array of relational data into a hierarchical structure

Pure data transformation - performes a series of nested group-by operations.

Type Safe - type inference intelligently decides nullability

Low Footprint - no dependencies, fewer than 100 lines of generated code

ORM-like object structure - without the ORM

import { nestedGroupBy } from 'nested-group-by-ts';
import { client } from './database';

type Office = {
  officeId: string;
  officeFloorNumber: number;
  employeeId: string;
  employeePhoneNumber: string | null;
};
const flatOffices: Office[] = await client.query(`
  SELECT
    o.id as officeId,
    o.floor_number as officeFloorNumber,
    e.id as employeeId,
    e.phone_number as employeePhoneNumber
  FROM office o
  INNER JOIN employees e on e.officeId = o.id
`);

const offices = nestedGroupBy(flatOffices, {
  groupBy: ["officeId"],
  select: ["officeFloorNumber"],
  joins: {
    // this custom name - 'employees' - is
    // passed along into the output
    employees: {
      groupBy: ["employeeId"],
      select: ["employeeId", "employeePhoneNumber"],
    },
  },
});

// here's the full auto-inferred type
// NEA stands for 'non-empty-array'

// offices: {
//   officeFloorNumber: number;
//   employees: NEA<{
//     employeeId: string;
//     employeePhoneNumber: string | null;
//   }>;
// }[]

Left Joins

Left joins yield nullable values

type Building = {
  buildingId: string;
  buildingAddress: string;

  // some buildings don't have a janitor
  // thus, the LEFT JOIN
  // that's why these values might be null
  janitorId: string | null;
  janitorStartDate: Date | null;
};
const flatBuildings: Office[] = await client.query(`
  SELECT 
    b.id as buildingId,
    b.address as buildingAddress,
    j.id as janitorId,
    j.start_date as janitorStartDate
  FROM building b
  LEFT JOIN janitors j on j.building_id = b.id
`);

const buildings = nestedGroupBy(flatBuildings, {
  groupBy: ["buildingId"],
  select: ["buildingAddress"],
  joins: {
    janitors: {
      // each janitor, if they exist, should have
      // a start date - so, group by start date as well
      groupBy: ["janitorId", "janitorStartDate"],
      select: ["janitorStartDate"],
    },
  },
});

// buildings: {
//   buildingAddress: string;
//   janitors: {
//     janitorStartDate: Date;
//   }[];
// }[]

// ^^^
// `janitors` is a "normal" array (not a non-empty-array)
// because `janitorId` is nullable
// `janitorStartDate` is non-null because we
// grouped by start date as well

Multiple Joins

type FullBuilding = {
  buildingId: string;
  buildingAddress: string;

  janitorId: string | null;
  janitorStartDate: Date | null;

  officeId: string;
  officeFloorNumber: number;

  employeeId: string;
  employeePhoneNumber: string | null;
};
const flatFullBuildings: Office[] = await client.query(`
  SELECT 
    b.id as buildingId,
    b.address as buildingAddress,
    j.id as janitorId,
    j.start_date as janitorStartDate,
    o.id as officeId,
    o.floor_number as officeFloorNumber,
    e.id as employeeId,
    e.phone_number as employeePhoneNumber
  FROM building b
  LEFT JOIN janitor j on j.building_id = b.id
  INNER JOIN office o on o.building_id = b.id
  INNER JOIN employee e on e.officeId = o.id
`);

const fullBuildings = nestedGroupBy(flatFullBuildings, {
  groupBy: ["buildingId"],
  select: ["buildingAddress"],
  joins: {
    janitors: {
      groupBy: ["janitorId", "janitorStartDate"],
      select: ["janitorStartDate"],
    },
    offices: {
      groupBy: ["officeId"],
      select: ["officeFloorNumber"],
      joins: {
        employees: {
          groupBy: ["employeeId"],
          select: ["employeeId", "employeePhoneNumber"],
        },
      },
    },
  },
});

// fullBuildings: {
//   buildingAddress: string;
//   janitors: {
//     janitorStartDate: Date;
//   }[];
//   offices: NEA<{
//     officeFloorNumber: number;
//     employees: NEA<{
//       employeeId: string;
//       employeePhoneNumber: string | null;
//     }>;
//   }>;
// }[]