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

@teambit/environments

v0.0.100

Published

# Creating a new Environment Before starting, it might be easier to re-use an existing environment, see the "Composing an Environment" section below.

Readme

This is a WIP, Please improve.

Creating a new Environment

Before starting, it might be easier to re-use an existing environment, see the "Composing an Environment" section below.

To create a new environment, create a new extension, add "teambit.environments/environments" as a dependency and register to its slot: envs.registerEnv(yourNewEnv);. See the provider of react.extension.ts for a detailed example.

The class of the environment extension needs to implement the Environment interface. For now, due to types/circular constrains, it doesn't require to implement anything. However, to get a working env, you must implement the following:

getBuildPipe(): BuildTask[];

There are the tasks that will be running on "bit tag"/"bit build". If you have a compiler setup, it should include this.compiler.task. Also, it is recommended to add the dry-run task of the publisher: this.pkg.dryRunTask. See the react.env.ts for a detailed example.

Also, it is recommended to implement the following:

getCompiler(): Compiler; // if you need compiler
getTester(): Tester; // if you need tester
getDependencies(); // if you need to change/add/remove package dependencies

Configure workspace to use the env

add this to your workspace.jsonc file.

"teambit.environments/environments": {
  "env": "your-new-env",
  "config": {}
}

Composing an Environment

TBD