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

parse-due-date

v1.0.0

Published

Parse human readable due dates

Downloads

12

Readme

parse-due-date

A JavaScript library for parsing human readable due dates.

Overview

parse-due-date will parse several formats of dates and intervals, such as "4/15" or "in 3 weeks". Because it concerns mostly with due dates, it will resolve ambiguity by selecting a date in the future instead of one in the past.

parse-due-date tries to resolve partial input, and return all possible resolutions. For example, "next t" will result in two entries, "next tuesday" and "next thursday".

Date parsing is US-centric, in that "1/2/2017" is treated as January 2nd, 2017.

Usage

Parameters

parseDueDate(string, {ref: refDate, endOfDay: false})
  • string
    • String to parse
  • ref
    • The Date object to use instead of now for relative dates
  • endOfDay
    • Return Date objects at the very end of the day, instead of very beginning. Defaults to false.

Output

parseDueDate returns an array of objects with the following shape:

  • date
    • Date object with the parsed date. This will be at the beginning or end of the day depending on endOfDay parameter.
  • match
    • The fully resolved string, with
  • string
    • String originally passed to parseDueDate

Example

const parseDueDate = require('parse-due-date')

const possibleDates = parseDueDate('in 2')

/* possibleDates = [ { date: 2017-05-06T07:00:00.000Z,
                       match: 'in 2 days',
                       string: 'in 2' },
                     { date: 2017-05-18T07:00:00.000Z,
                       match: 'in 2 weeks',
                       string: 'in 2' },
                     { date: 2017-07-04T07:00:00.000Z,
                       match: 'in 2 months',
                       string: 'in 2' },
                     { date: 2019-05-04T07:00:00.000Z,
                       match: 'in 2 years',
                       string: 'in 2' } ]
*/

Supported formats

See parseDueDate.spec.js for details. A general list:

  • "in 1 week"
  • "in 2 days"
  • "in 10 months"
  • "today"
  • "tomorrow"
  • "next friday"
    • Friday of next week
  • "this tue"
    • Tuesday of this week, or next week if that's in the past
  • "tuesday"
    • Tuesday of this week, or next week if that's in the past
  • "15th"
    • 15th of this month, or next month if that's in the past
  • "7/12"
    • July 12th of this year, or next year if that's in the past
  • "9/12/2020"
  • "1/12/19"
  • "May 12th"
    • May 12th of this year, or next year if that's in the past
  • "Dec 29, 2019"