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

@dopt/please

v1.0.8

Published

A CLI for developing in monorepos - not building them

Downloads

4

Readme

Please

A CLI for developing in monorepos - not building them

Why

Because developing in monorepos can be challenging. There are great tools for building them (e.g. turbo, bazel, rush, gradle, etc) but the experience of developing in them often involves lots of manual effort.

By developing, I mean, running/executing code. For example, consider our own experience at Dopt. A typical workflow for basic feature development in our application involved running commands across 10+ packages to start various services and their databases.

Depending on what you were focused on, certain packages would need to be started in different ways, e.g., w/ file-watchers versus without.

In practice, this meant lots of windows and lots of commands. A situation that made it easy to miss an error stack or an important log.

Introducing please

A simple, compact, and expressive CLI for running package scripts across packages with interleaved output. The above scenario was transofmred into the following

please start:service-x,service-y,service-z dev:{app-*} up:{database-*}

Install

# w/ pnpm
pnpm add -Dw please

# w/ yarn
yarn add -D please

# w/ npm
npm install -D please

Usage

Basic:

  $ please dev:@scope/package-1 run:@scope/package-2

  $ please dev:@scope/package-1 run:@scope/package-2,@scope/package-3

  $ please dev:@scope/package-1,@scope/package-2 run:@scope/package-3,@scope/package-4

Advanced:

  $ please dev:{@scope/*}

  $ please dev:{@scope/*} run:package-1,package-2