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

@softwareventures/yarn-recursive

v5.0.55

Published

Recursively run yarn in a folder. Fork of original with bug fixes, and performance and sanity patches.

Downloads

255

Readme

yarn-recursive

Recursively run yarn in a folder

Takes your tree and checks for package.json in every folder and runs yarn in every folder.

This is a fork of the original project, with bug fixes, and performance and sanity patches.

Usage

$ yarn-recursive [options] [--] [command] [yarn-options]

Recursively runs yarn in the current working directory.

Arguments for yarn-recursive and yarn may be freely mixed on the command line. Any argument not handled by yarn-recursive will be passed through to yarn as-is.

For example:

$ yarn-recursive install

Recursively runs yarn install in every subdirectory that contains a package.json, including the current directory.

You can also specify a -- argument on its own to let yarn-recursive know that it should not attempt to process the subsequent arguments. If there are any arguments after the -- argument, then they will be passed through to yarn as-is. This is useful in case in the future yarn gains options that have the same name as options handled by yarn-recursive. In this way you can force yarn-recursive to pass through the option.

For example:

$ yarn-recursive --skip-root -- install --include-hidden

Recursively runs yarn install --include-hidden in every subdirectory that contains a package.json, excluding the current directory. The include-hidden option is passed through to yarn even though it would normally be handled by yarn-recursive. (But note that yarn doesn't have an option called --include-hidden, so this will fail.)

Skip root

If you want to skip the root directory of your project, add the --skip-root option:

$ yarn-recursive --skip-root test

Runs yarn test in every subdirectory that contains a package.json, excluding the current directory.

This is useful if, for example, you want to run yarn-recursive from a script in your root package.json, which would otherwise cause infinite recursion.

Hidden Directories

By default, yarn-recursive will not search inside hidden directories (directories with names that start with a dot, for example .git).

If you want to include hidden directories in the search, specify the --include-hidden option, for example:

$ yarn-recursive --include-hidden

Concurrency

By default, yarn-recursive will run yarn for each project sequentially.

To run yarn for all projects concurrently, specify the --concurrent option, for example:

$ yarn-recursive --concurrent start

This is particularly useful for commands like yarn start which may not exit until the user stops them.

This feature is not recommended for general build tasks such as yarn install, since output from each concurrent process will be interleaved in the console and likely be difficult to read.

This feature is experimental and will be improved in future releases.