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

prepare-workspace-modules

v0.3.0

Published

## situation:

Downloads

2

Readme

prepare-workspace-modules

situation:

you have a monorepo using npm v7+ workspaces, and some of your modules are written in typescript or otherwise require a compilation or bundling step before being consumed by other modules.

problem:

npm v7 currently has a bug which results in lifecycle scripts not executing in packages.

this means that if one of your packages' exports does not exist until after the prepare script is run, other packages will not be able to consume that package until you manually cd into the package directory and run it yourself. very annoying!

you also can't just run npm run --workspaces prepare because the command has no knowledge of the dependency graph. you must manually take into account the heirarchy of your modules.

solution:

run this package in the root directory.

also, if you want to run another script other than "prepare", you can provide said script as an argument. thank you @jimmed for the PR!.

how it works:

this package will first inspect your root module's package.json to discover all workspaces in the project. it actually uses the same @npmcli/map-workspaces module that npm uses internally.

also, instead of including that package as a dependency, this tool will discover the installed map-workspaces implementation from your global npm installation, so hopefully it should Just Work™ with newer versions of npm.

the tool then inspects your project's dependencies and does a post-order depth-first search on the dependency tree, executing the prepare script in each package, leaves first.