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

module-replacements

v2.5.0

Published

This package provides a set of manifests which each define a mapping of JS modules to their suggested replacements.

Downloads

51,017

Readme

module-replacements

As part of the community e18e effort, this project provides a collection of module replacements (i.e. possible alternative packages).

We provide two things:

  • Manifests (mappings of modules to their possible replacements)
  • Documentation for more complex replacements

List of replacements

You can find a list of replacements in the modules readme.

Tools

Some tools consume the lists of modules in this repository:

| Name | Description | | -- | -- | | eslint-plugin-depend | ESLint plugin to detect possible replacements |

Manifests

The manifests can be used via the module-replacements npm package.

We provide three manifests:

  • All (includes every manifest)
  • Native replacements
  • Micro utility replacements
  • Preferred replacements

Usage

You can install this package via npm:

npm i -S module-replacements

You can then import the manifest of your choice:

import {nativeReplacements} from 'module-replacements';

The manifests are also available directly in the manifests/ directory of the package (e.g. node_modules/module-replacements/manifests/native.json).

Native replacements (nativeReplacements, native.json)

These are modules which can now be replaced by native functionality.

For example, pseudo-polyfills which provide functionality of widely available platform features can be replaced by their platform equivalents.

Similarly, features which did not exist at the time but have now existed in the platform for many years, so no longer need a dependency.

Micro utility replacements (microUtilsReplacements, micro-utilities.json)

This is a more opinionated list of modules considered to be 'micro utilities' - very small utilities which could possibly be replaced with native equivalents or removed entirely.

Preferred replacements (preferredReplacements, preferred.json)

This is a very opinionated list of modules with preferred replacements. Often these replacements are much lighter or more modern than the modules they are replacing.

Sometimes these may also be actively maintained forks of older, unmaintained source packages.

Contributing

If you would like to add a replacement mapping to one of the manifests, please open an issue where this can be discussed.

Keep in mind, very newly available native features are unlikely to join the list since they are not widely available yet.