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

shared-package-module-resolver-plugin

v0.0.2

Published

A webpack custom resolver plugin to route module resolutions to the root issuer

Downloads

9

Readme

Webpack SharedPackageModuleResolverPlugin

This is a webpack resolve plugin for a very specific case: When you're running multiple packages into a single project (a monorepo) and want one of the packages to rely on the dependencies of the other packages.

Reasoning

Consider this monorepo project structure:

packages/
├── appA/
│   ├── node_modules/
│   │   ├── [email protected]
│   │   └── [email protected]
│   └── app.js
│
├── appB/
│   ├── node_modules/
│   │   ├── [email protected]
│   │   └── [email protected]
│   └── app.js
│
└── lib/
    ├── card.js
    └── button.js
  • appA uses react 17 and lodash 5
  • appB uses react 15 and lodash 5
  • lib is a package of reusable components
  • appA/app.js imports lib/card.js
  • appB/app.js also imports lib/card.js
  • lib/card.js imports react and lodash

The outcome without this plugin:

  • lib/ has to install its own dependencies or rely on the root node_modules folder
  • in the case of react, appA and appB are using different versions, so lib/ will be incompatible with one of them.
  • in the case of lodash, appA and appB are using the same version, but lib/ can't use them. we'll endup with two copies of the same lodash version in the bundle

The outcome with this plugin:

  • lib/ does not have to install its own dependencies
  • when requested by appA, lib/* will resolve its modules from appA
  • when requested by appB, lib/* will resolve its modules from appB
  • we solve both issues: no duplicated lodash and no conflicting react versions

Instalation

npm install --save-dev shared-package-module-resolver-plugin

Usage

import SharedPackageModuleResolverPlugin from 'shared-package-module-resolver-plugin'

module.exports = {
  ...
  resolve: {
    // note this is a resolver plugin, so it goes inside resolve.plugins, not inside the main plugin object
    plugins: [new SharedPackageModuleResolverPlugin({
      packagesPath: path.join(__dirname, 'packages') // This has to be the absolute path!,
      sharedPackage: 'lib', // do not add slashes or anything else. just the name of the package
    })]
  }
}