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

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';

We provide three manifests:

• All (includes every manifest)
• Native replacements (modules which can be replaced by native equivalents)
• Optimisation replacements (modules which can be replaced by leaner or closer-to-the-platform equivalents)

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.

These are modules which have more optimal replacements.

For example, some modules have arguably unnecessarily deep dependencies trees, or rely on functionality themselves which fit into the "Native replacements" category. These should likely be replaced by leaner alternatives.

Another example - modules which are too granularly modularised, leading to unnecessarily large amounts of small dependencies (aka "micro dependencies").

Due to this being a one-to-many mapping (there are often many possible replacements), this list can contain multiple replacements per module.

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.