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

@iamproperty/reapit-elements

v1.0.0

Published

## Local Development

Downloads

27

Readme

Elements

Local Development

To test your changes within a project you should add the repository config below to your composer.json repositories property. It should be added as the fist repository so that Composer will use it before any published version.
Please don't commit these changes to composer.json or changes to composer.lock based on these changes.

The symlink property is important when running within Docker because the container won't have access to this package and the files won't be found within the container when looked for. When running in this way you can use composer reinstall iamproperty/reapit-elements to update your latest changes.

If you wanted to have instant changes you should be able to mount this project into your container.

{
    "type": "path",
    "url": "<path to this package>",
    "options": {
        "symlink": false
    }
}