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

monolinter

v1.0.5

Published

Collection of utilities to lint files accross mono repos

Downloads

89

Readme

Monolinter

When woriking in a monorepo, often we find that some subprojects's package dependencies diverge, leading to unexpected results. Monolinter reads all provided package.json's files and validates their consistency. The validation can be run as part of your CI/CD process.

Note: validations are useful / can be applied even if your project only has one package.json

Monolinter was designed to be modular and easily extensible with validation modules

Validation Modules:

  • Consistent package versions: Checks that packages declared accross subprojects have matching versions. For example if app1/package.json has a dependency to depA version 1.0.0 but app2/package.json has a dependency to depA version 2.0.0 the validation will fail

  • Duplicate packages: withing the same file, it prevents duplicate declaration of the same package, this happens accross devDependencies and dependencies. If the same dependency depA is found more than once in dependencies of package.json.

  • Exact package versions: prevents using fuzzy versions (starting with ^ or ~) that might cause inconsistent builds. For example if package.json contains depA version ^1.0.0 this validation will fail as ^1.0.0 might lead to inconsistencies.

  • Related packages: some packages should have matching versions. For example "react-native-web" and "babel-plugin-react-native-web". Hoever there's no way to enforce that until now. Please contribute more such packages to this repo.

Installation

yarn add monolinter -d

Usage

Create a file called .monolinterrc in your root folder with the following configuration:

{
 "include":["package.json","mypackagespath/**/package.json"]
}

the included paths can be glob expressions.

In order to run from command line, you can call it directly instead

yarn monolinter package.json [list of globs to other package.json files]

Contributing

Contributions are welcome, please create a PR, open an issue or start a discussion.

Tutorial Credits for creating this package: https://itnext.io/step-by-step-building-and-publishing-an-npm-typescript-package-44fe7164964c

https://medium.com/wizardnet972/write-a-simple-node-executable-with-typescript-and-vscode-97c58adca02d

https://medium.com/jspoint/creating-cli-executable-global-npm-module-5ef734febe32