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

luxon-next

v0.0.21

Published

An experimental rewrite of Luxon.

Downloads

51

Readme

An experimental rewrite of Luxon.

Ideas here

  1. Make tree-shaking work by dispensing with classes and being careful about dependency structure
  2. Support chaining using JS pipe operators (presumably the hack variety)
  3. Typescript all the things
  4. Calendar extensibility (though not parser and formatter extensibility)
  5. Clearer control of memoization
  6. Fewer things are "part" of the core objects, such as locale and conversionAccuracy, and are instead always arguments to particular functions, or global defaults

Caveat Emptor!

This is completely experimental. If you use this for anything real, you are making a mistake.

The future of this code is very much in doubt:

  1. The Temporal API (a much-improved native Date API for the browser) is now in Stage 3. It should obviate most of the need for a library like Luxon and may cause me to shelve it altogether. At the very least, I will happily chuck a ton of the code here.
  2. I'm working on this while I have some time off, which I'll eventually stop having. I also may simply move onto other stuff. Creating a new date/time library no one asked for is a lot of work!