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

lerna-script-tasks-modules

v1.4.0

Published

module version sync task for lerna-script

Downloads

566

Readme

lerna-script-tasks-modules

Syncs dependencies/devDependencies/peerDependencies for modules within repo.

install

npm install --save-dev lerna-script-tasks-modules

Usage

Say you have modules:

  • /packages/a with version 1.0.0
  • /packages/b with version 1.0.0 and it depends on module a where {dependencies: {"a": "~1.0.0"}}

and you up the version of /packages/a to 2.0.0. If you want for version of a to be in sync in module b, then you could do:

//lerna.js
const syncModules = require('lerna-script-tasks-modules')

module.exports['modules:sync'] = syncModules()

and then upon executing lerna-script modules:sync version of dependency a for module b will be set to ~2.0.0. Same goes for devDependencies and peerDependencies.

API

({packages: [], transformDependencies: version => version, transformPeerDependencies: version => version})(log): Promise

Returns a function that syncs module versions across repo.

Parameters:

  • packages, optional = list of lerna packages. Loads defaults of not provided.
  • transformDependencies, optional = function to transform dependencies and devDependencies. Defaults to version => '~' + version.
  • transformPeerDependencies, optional - function to transform peerDependencies. Defaults to version => '>=' + version.