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

@everyonesoftware/common

v45.0.0

Published

A package containing common code for everyonesoftware projects.

Downloads

2,000

Readme

Everything

Concept

The everything folder contains all of my TypeScript source code. The intention is that all source code for a specific language could be in the same folder and that different applications would just pull in the source files that they need. This would eliminate the need for libraries, which should make bundling easier and more efficient. It should also improve build and test times since making changes (changing source code, building, and then testing) would immediately appear in other projects.

Challenges

The biggest challenge I can think of is that the current TypeScript tooling doesn't support this approach. All of the existing tooling (such as npm, yarn, pnpm) only support single-folder packages. Some support mono-repo packages, but what I'm describing isn't a mono-repo. Technically, yes, my idea is that multiple projects would exist in the same folder, but mono-repos have a root directory where common configuration goes and then sub-folders for each different project. My approach is different from this in that I want a single source code folder. Project configuration files would go into the root of the repository. Source code files would be compiled and tested whenever they're changed. Finally project outputs (such as executable files or bundled websites) could either automatically be packaged or they could be packaged on demand later.