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

multirepo-build-deps

v1.0.5

Published

When working with code split amongst multiple repositories, an effective strategy can be to add package.json dependencies referencing git repos directly, such as:

Downloads

12

Readme

multirepo-build-deps

When working with code split amongst multiple repositories, an effective strategy can be to add package.json dependencies referencing git repos directly, such as:

"@myorg/my-other-repo": "git://github.com/myorg/my-other-repo.git#v1.0.0",

or to reference in-progress work on a feature branch

"@myorg/my-other-repo": "git://github.com/myorg/my-other-repo.git#feature/a-feature-branch",

However, the issue with this strategy occurs when the code in that repo needs to be built/transpiled in order to be used by the dependent repo. For example, code written in TypeScript needs to be transpiled to js, and code using it will likely rely on types that are only generated at build time.

This package provides a simple script that can be used to run a yarn script on a package inside node_modules to prepa

requirements

This package currently relies on yarn being installed (the shell scripts here use yarn internally to install dependencies and run scripts).

build-deps

This script assumes that you are installing multiple dependencies scoped for an organization, and will process each sub-package inside that org and execute a build script for that repo.

The most effective way to use this script is to add it as the postinstall script inside package.json

    "postinstall": "build-deps @myorg"

By default, this will execute yarn and run the command build. A second parameter can be provided to choose a different command

    "postinstall": "build-deps @myorg another-command"

watch-deps

This scripts is useful when you have multiple dependencies inside an org that you have symlinked using yarn link during development. It allows you to run a single command to trigger a watch inside all linked dependency repos for the org.

Example usage: yarn watch-deps $myorg

Note that this will only trigger the watch command if the dependency is found to be a link. This assumes that for a non-linked package that a one-time build on install (build-deps) will suffice.

    "watch-deps": "watch-deps @myorg"

OR

    "watch-deps": "watch-deps @myorg my-watch-command"