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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@olympeio-extensions/lab

v2.7.0

Published

This project is made for the Olympe community to be able to create coded bricks (logic and visual) and deploy them to the community environment.

Readme

Olympe LAB Extension

This project is made for the Olympe community to be able to create coded bricks (logic and visual) and deploy them to the community environment.

How to participate

  1. First register to the community following the instructions on the support website.
  2. Code your bricks and test them locally.
  3. Send a message on discord to join the "Olympe Community" team on Github to become a contributor of this project.
  4. Create a pull request with your code:
    1. clone this repository
    2. create a branch based on the develop branch. Name it like this: <community username>-<bricks set name>
    3. create a pull request of your branch to the develop branch. Ensure that you respect the structure specified in the rules.

Rules

This is a public repository, so all the code you will push will be publicly visible. This also means that you will share src folder with others.

Here are the rules and the folder structure you need to follow in order to have accepted pull requests:

  1. Nothing outside the src folder will be accepted.
  2. Inside the src folder, you will see 3 folders:
    1. common: contain all files added to both Browser and NodeJS bundles. It MUST be code that works on both environments.
    2. web: contain all files added ONLY to the Browser bundle. It will typically contain the visual components.
    3. node: contain all files added ONLY to the NodeJS bundle. It will typically contain logic bricks that use backend libraries.
  3. Inside the 3 sub-folders, you must put your files in a folder named using your GitHub username. We won't accept any change coming from a user that update files in another folder than its own.
    • Example: my username on GitHub is john.smith, I'll add my visual component js files into src/web/john.smith folder.
  4. All source files are written in javascript or typescript.