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

@corex/ywc

v3.0.611

Published

- commands : string[]

Downloads

360

Readme


title: '@corex/ywc' custom_edit_url: 'https://github.com/iamvishnusankar/corex/edit/master/packages/ywc/README.md'

Local Automator for yarn workspaces. Yarn-Workspace-Commands lets you to run a set of commands for local dev/ci build on all workspace packages folder.

Options

  • commands : string[]

  • excludePrivatePackages : boolean

Basic Usage

Install package on workspace root

yarn add @corex/ywc -D -W

Define commands ywc.config.json

{
    "[command_key]": {

         /* Array of commands to execute */
        "commands": "string[]",

        /* Execute only on root folder. Default : false */
        "rootCommand": "boolean"
    }
}

Execute

# command_key defined in ywc.config.json
yarn ywc <command_key>

Detailed Setup Instructions

1. Setup Yarn Workspace

For further info on setting up yarn workspace : Setting Up Yarn Workspace

{
  "private": true,
  "workspaces": ["packages/*", "app/*"]
}

or

{
  "private": true,
  "workspaces": {
    "packages": ["packages/*", "app/*"],
    "nohoist": []
  }
}

2. Install Package

yarn add @corex/ywc -D -W

3. Create ywc.config.json in workspace root

Set rootCommand : true to make the commands run only on root folder.

{
  "test_command_1": {
    "commands": [
      "echo command 1",
      "echo command 2",
      "echo command 3",
      "echo command 4"
    ]
  },
  "test_command_2": {
    "commands": ["echo command 5", "ls"]
  },
  "test_command_3": {
    "commands": ["yarn test_root_command"],
    "rootCommand": true
  }
}

4. Add script to package.json in workspace root

{
  "scripts": {
    "test_ywc": "ywc test_command_1 test_command_2 test_command_3",
    "test_root_command": "echo hello world root command"
  }
}

5. Run the commands

yarn test_ywc

Practical Example

If you have a yarn workspace and want to perform a clean build of all local packages after the installation of new modules.

  • Add the following to ywc.config.json

    {
      "build": {
        "commands": ["yarn build"]
      },
      "clean": {
        "commands": ["rm -rf dist", "rm -rf build"]
      }
    }
  • Add the following script to package.json in workspace root

    {
      "scripts": {
        "postinstall": "ywc clean build"
      }
    }

Environment Variables

Since the command execution is taking place under node environment, All environment variables available to process.env can be used as inline arguments.

Example : Package versioning

  • ywc.config.json

    {
      "test-env": {
        "commands": ["echo ${NODE_ENV} ${NODE}"]
      },
      "set-version": {
        "commands": ["npm version --no-git-tag-version ${BUILD_BUILDNUMBER}"]
      }
    }
  • Add the set version script to package.json

    {
      "scripts": {
        "set-version": "ywc set-version"
      }
    }
  • Run the command to update version of all packages

    yarn set-version