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

@flow48/mfe-loader

v0.2.6

Published

Helper library for loading micro frontends in Flow48 applications

Readme

@flow48/mfe-loader

MFELoader is a lightweight React component designed to load micro frontends (MFEs) dynamically inside a host React application using Qiankun. It simplifies mounting, unmounting, and prop passing, allowing easy integration of micro frontends.


Features

• Dynamically load micro frontends based on app name and entry.
• Pass props from the host application to the micro frontend.
• Automatic mounting and unmounting.
• Supports multiple independent instances of the same micro frontend.
• Type-safe integration for React + TypeScript.

Usage

  1. Basic usage
import { MFELoader } from 'mfe-loader';

export const MFEDmsLoaderExample = () => {
  return (
    <MFELoader
      app="dms"
      name="MFEDmsLoaderTest1"
      props={{
        initialPath: '/account-documents',
        testProp: 'Test Value',
      }}
    />
  );
};
• app: The unique name of the micro frontend you want to load.
• name: A unique identifier for this instance (used internally by Qiankun).
• props: An object with props to pass to the micro frontend.

  1. Passing props to specific components
<MFELoader
  app="dms"
  name="MFEDmsLoaderTest1"
  props={{
    initialPath: '/account-loan-documents',
    sfWidgetProps: {
      userId: '12345',
      theme: 'dark',
    },
  }}
/>

Inside the sub-app, the sfWidgetProps can be forwarded to a specific component:

<Route
  path="/account-loan-documents"
  element={<SfWidget {...props.sfWidgetProps} />}
/>

  1. Multiple instances

Render multiple instances of the same micro frontend by providing a unique name:

<MFELoader app="dms" name="MFE1" props={{initialPath: '/doc1'}} />
<MFELoader app="dms" name="MFE2" props={{initialPath: '/doc2'}} />

Each instance maintains its own state and container.


Notes

• Ensure the sub-app implements Qiankun lifecycle methods (bootstrap, mount, unmount) and accepts props.
• Avoid calling render() inside update() in the sub-app to prevent overwriting the host app.
• For dynamic prop updates, use state management or context inside the sub-app.

Helper


Installation

Make sure your project uses the correct npm registry for the Flow48 organization:

Create a file .npmrc

@flow48:registry=https://registry.npmjs.org/

Then install the package via npm or yarn:

Publishing

npm version patch  # 0.1.0 → 0.1.1
npm version minor  # 0.1.0 → 0.2.0
npm version major  # 0.1.0 → 1.0.0
  1. Login to npm (must have access to @flow48 org):
npm login
  1. Build the library
yarn build:prod
  1. Publish the package
# Public package
npm publish --access public

# Or restricted to org members
npm publish --access restricted
  1. Verify the published package
npm info @flow48/mfe-loader
  1. Push the version tag to remote
yarn add @flow48/mfe-loader