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-federation-plugin

v0.8.4

Published

Module federation for webpack@4

Downloads

1,604

Readme

module-federation-plugin

Module federation for webpack@4.

This project is forked from alibaba/module-federation4.

WARNING: This package is not yet stable and implements only a very limited number of features in the standard module federation. Please take special care before using it in a production environment.

Usage

npm install --save-dev module-federation-plugin

Expose modules in containers

// webpack.config.js
const { ModuleFederationPlugin } = require('module-federation-plugin')

module.exports = {
  output: {
    publicPath: 'http://localhost:3002/',
  },
  plugins: [
    new ModuleFederationPlugin({
      name: 'website-2',
      filename: 'remoteEntry.js',
      exposes: {
        foo: './src/foo.js',
      },
      // library: {
      //   type: 'var',
      //   name: 'website-2',
      // },
    }),
  ],
}

Import modules from remote containers

You can use the shortcut syntax in webpack v5.

// webpack.config.js
const { ModuleFederationPlugin } = require('module-federation-plugin')

module.exports = {
  output: {
    publicPath: 'http://localhost:3001/',
  },
  plugins: [
    new ModuleFederationPlugin({
      name: 'website-1',
      remotes: {
        '@website-2': 'website-2@http://localhost:3002/',
      },
      // remoteType: 'script',
    }),
  ],
}

Or you can reference the container entry file in the HTML entry manually.

// webpack.config.js
const { ModuleFederationPlugin } = require('module-federation-plugin')

module.exports = {
  output: {
    publicPath: 'http://localhost:3001/',
  },
  plugins: [
    new ModuleFederationPlugin({
      name: 'website-1',
      remotes: {
        '@website-2': 'website-2',
      },
      remoteType: 'global',
    }),
  ],
}
<html>
  <head>
    <script src="http://localhost:3002/remoteEntry.js"></script>
  </head>
  <body>
    <div id="app"></div>
  </body>
</html>

You can use the import() call to reference these modules.

import('@website-2/foo')
  .then(({ xyz }) => {
    // ...
  })

Additional Features

In addition to the module federation itself, this plugin also provides the additionalFeatures option to support some additional features.

No Additional Chunks

An asyncChunkMode option can be passed to the plugin to specify the default chunk mode of remote modules.

// webpack.config.js
const { ModuleFederationPlugin } = require('module-federation-plugin')

module.exports = {
  plugins: [
    new ModuleFederationPlugin({
      // ...
      additionalFeatures: {
        asyncChunkMode: 'eager',
      },
    }),
  ],
}
// In this case the following code
import('@website-2/foo')

// will be equivalent to
import(/* webpackMode: 'eager' */'@website-2/foo')

// which will not create extra asynchronous chunks

No Static Imports

By default, an asynchronous module will be replaced with a synchronous one after loaded. This may be useful if you prefer static imports.

// In the entry file
import('@website-2/foo').then(() => import(/* webpackMode: 'eager' */'/path/to/the-real-entry-file'))

// OR
// import('@website-2/foo').then(() => require('/path/to/the-real-entry-file'))
// In the real entry file
import { MyComponent } from '@website-2/foo';

A keepAsync option can be passed to the plugin if you wish to disable the feature.

// webpack.config.js
const { ModuleFederationPlugin } = require('module-federation-plugin')

module.exports = {
  plugins: [
    new ModuleFederationPlugin({
      // ...
      additionalFeatures: {
        keepAsync: true,
      },
    }),
  ],
}

Migrate to webpack>=5

Simply perform the following steps in sequence:

  1. Modify the import path of the plugin.
+ const { ModuleFederationPlugin } = require('webpack').container
- const { ModuleFederationPlugin } = require('module-federation-plugin')
  1. Remove the additionalFeatures option and modify the code that depends on these features.
module.exports = {
  plugins: [
    new ModuleFederationPlugin({
      // ...
-     additionalFeatures: {/* ... */},
    }),
  ],
}
  1. Run and test to confirm that the relevant functions are working properly.