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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@muritavo/microfrontend-webpack-plugin

v0.0.2

Published

A plugin that setups the imports required for the proposed implementation of the microfrontend architecture

Readme

@muritavo/microfrontend-webpack-plugin

This plugin works by injecting a bootstrap function to the stratup chunk. This function registers the necessary import maps and the necessary tags.

Usage

Required dependencies

It's required to put the following dependencies in this specific order on the entry point of the application (usually index.js):

Install the dependencies as required

import "import-map-overrides"; 
import "systemjs/dist/system";
import "systemjs/dist/extras/use-default";
import "systemjs/dist/extras/amd";
import "systemjs/dist/extras/named-register";
import "systemjs/dist/extras/named-exports";

This will setup the required dependencies for dynamically importing the dependencies

Webpack configuration

For pointing to a microfrontend chunk it's required to indicate the microfrontend definition on the webpack plugins configuration like the following:

const MicrofrontendWebpackPlugin = require('@muritavo/microfrontend-webpack-plugin')
{
    //...all the rest of the configuration
    plugins: [
        new MicrofrontendWebpackPlugin([ //As an argument it receives an array with the definition of all the referenced microfrontends
            {
                name: 'mfe-XXX', //The name used when importing the microfrontend on the application\
                chunkLocation: 'http://pudim.com.br', //The location of the microfrontend chunk with the microfrontend definition
                externals: { //The shared dependencies through the referenced microfrontends. Required so dependencies are not unecessarly bundled on multiple applications.
                    'DependencyOne': 'CDN',
                    'DependencyTwo': 'CDN'
                }
            },
            //...Other definitions
        ])
        //...other plugins
    ]
}

Referencing the microfrontend on the code:

React

For referencing other microfrontends inside a React application you can use the single-spa-react component 'Parcel'


import Parcel from 'single-spa-react/Parcel';
import {mountRootParcel} from 'single-spa';

//...Inside the render routine

//As a config property you pass a function that return a import promise from SystemJS
//The imported name should match the provided name on the webpack plugin microfrontend definition

//The other props will be passed as the propos for the root component of the microfrontend (if done in react)
<Parcel config={() => window.System.import('mfe-XXX')} mountParcel={mountRootParcel} {...otherProps}/>