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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@greenstreet/parsers

v1.0.2

Published

A Library of string to data-type parsers

Downloads

6

Readme

Parsers

A Library of string to data-type formatters

Build

Run npm run build to build the project. The build artifacts will be stored in the dist/ directory.

Running unit tests

Run npm run test to execute the unit tests via Jest.

Parsers

parseDate takes an "any" and an optional culture string (defaults to en-US). Returns a date object

  • The input can be a formatted date like 12/31/2020
  • The input can be a formatted date like 12-31-2020
  • The input can be an unformatted date like 12312020 or 123120
  • If the input is already a Date object, it'll return that object.
  • If the input is neither a string or a Date object, it'll return a null

parseISODate takes an "any" and returns a date object

  • If the input is null, the output will be null
  • If the input can't be parsed to a valid date, the output will be null

parseNumber takes an "any" and an optional culture string (defaults to en-US). Returns a number

  • The input will be parsed using the culture passed in.
  • If the input is null, the output will be null
  • If the input can't be parsed to a valid number, the output will be null