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

task-slotter

v0.2.0

Published

Pure-function task scheduler: fits tasks into free time windows by deadline and priority.

Readme

task-slotter

test npm

Fit tasks into your free time. A tiny, dependency-free scheduler that places tasks around busy blocks by deadline and priority.

Live demo

Install

Ships with TypeScript types, no @types package needed

npm install task-slotter

Usage

import { schedule } from "task-slotter";

const result = schedule(
  [
    { id: "dsa",    title: "DSA practice", duration: 90, priority: 1, deadline: "2026-10-25T18:00" },
    { id: "report", title: "SE report",    duration: 60, priority: 2 },
  ],
  {
    start: "2026-10-24T09:00",
    end:   "2026-10-24T21:00",
    busy:  [{ start: "2026-10-24T13:00", end: "2026-10-24T14:00" }],
    breakMinutes: 10,
  }
);

// result.scheduled   -> [{ id, start, end }]
// result.unscheduled -> [{ id, reason }]

API

schedule(tasks, options)

| Task field | Type | Notes | |---|---|---| | id | string | required | | duration | number | minutes, required | | priority | number | 1 = most important, default 5 | | deadline | string | optional, YYYY-MM-DDTHH:mm |

| Option | Type | Notes | |---|---|---| | start, end | string | the scheduling window | | busy | {start, end}[] | blocked time, may overlap | | breakMinutes | number | gap after each task, default 0 | | workingHours | {start, end} | "HH:mm" daily window; tasks only land inside it. Multi-day ranges work. |

Returns { scheduled, unscheduled }. Unscheduled reasons: "no free slot long enough" or "would miss deadline".

getFreeWindows(start, end, busy)

Returns the free gaps between busy blocks as {start, end} millisecond timestamps.

How it works

  1. Subtract busy blocks from the window with a left-to-right sweep (O(b log b)).
  2. Sort tasks by earliest deadline, then priority (O(n log n)).
  3. Place each task greedily in the first window that fits.

Limitations

Greedy first-fit is fast but not optimal. Fitting tasks into windows is a bin-packing variant, so some inputs have a valid arrangement this will miss. no task splitting and no overnight working hours

License

MIT