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

parcel-resolver

v0.0.0

Published

Hi there

Downloads

5

Readme

Hi there

It is against npm's package name policy to squat on package names. However, the Parcel team is actively designing Parcel 2.0 which includes plans to use this package name.

Because we have squatters who are actively taking npm package names and scopes from us we needed to reserve this package name for ourselves. We apologize for having to break npm's rules. We wouldn't have if the situation were different.

If we end up not using this package name for whatever reason after the first few Parcel 2.0 releases, we will happily hand it over to whoever wants it.

Please contact "me [at] thejameskyle [dot] com" or "devongovett [at] gmail [dot] com" if you would like ownership over this package name.