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

@azu/lerna-to-typescript-project-references

v1.0.4

Published

Keep package dependencies synchronized between lerna and typescript.

Downloads

5

Readme

lerna-to-typescript-project-references npm version

Keep package dependencies synchronized between Lerna and TypeScript.

This simple script runs over packages in a Lerna monorepo, and matches local package dependencies to project references within TypeScript config files.

By default it'll exit and return an error when a mismatched dependency is found. This is useful for CI scenarios, where you may want to avoid merging a change where you've mistakenly added an unmatched dependency.

With the update flag set, lerna-to-typescript-project-references will update TypeScript config files to match the dependencies found in the package files.

Command Line Usage

Usage: lerna-to-typescript-project-references.js [options]

Options:
  --update [boolean]           # Whether to write updates to ts config files.
  --tsConfigFileName [string]  # Set a custom name for your ts config file.  eg. tsconfig.dist.json

Examples

With no options, and configuration file in need of updating.

> lerna-to-typescript-project-references

@example/pkg1 - 0 dependencies found.
@example/pkg2 - 1 dependencies found. All match project references in tsconfig.json.
**FAIL** - @example/pkg3 - Some dependencies didn't match.
**FAIL** - @example/pkg3 - From npm packages: ../pkg1,../pkg2
**FAIL** - @example/pkg3 - From tsconfig.json: ../pkg1
npm ERR! code ELIFECYCLE

We can see from the output that the tsconfig.json file in pkg3 is missing a reference to ../pkg2. To have lerna-to-typescript-project-references update it for us, we can run it again, with the update flag enabled.

> lerna-to-typescript-project-references --update

@example/pkg1 - 0 dependencies found.
@example/pkg2 - 1 dependencies found. All match project references in tsconfig.json.
**UPDATE** - @example/pkg3 - Some dependencies didn't match. Writing 2 dependencies to tsconfig.json.

Now if run without options again, the script completes without error since all the dependencies match.

> lerna-to-typescript-project-references --update

@example/pkg1 - 0 dependencies found.
@example/pkg2 - 1 dependencies found. All match project references in tsconfig.json.
@example/pkg3 - 2 dependencies found. All match project references in tsconfig.json.