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

mf-test-pkg

v2.0.6

Published

This is a micro-frontends common module base on Single-spa for widget2.0 to load widget sub app.

Readme

@widget/micro-frontends-static

This is a micro-frontends common module base on Single-spa for widget2.0 to load widget sub app.

📦 Install

$ npm install @widget/micro-frontends-static

🔨 Usage

1、import at the entrance of container app

// index.tsx
import { microFrontend } from '@widget/micro-frontends-static';

microFrontend
	.registerApp({
		url: 'http://localhost:5001/',
		name: 'sub-app',
		library: 'microFrontend',
		active: true
	})
	.launch();

2、Use components in sub-apps

import React from 'react';
import ReactDOMClient from 'react-dom/client';
import App from './App';
import { subAppWrapper } from '@widget/micro-frontends-static';

const reactLifecycles = subAppWrapper({
	React,
	ReactDOMClient: ReactDOMClient,
	renderType: 'createRoot',
	rootComponent: App,
	domElementGetter: () => document.getElementById('react-app')!
});

export const { bootstrap, mount, unmount } = reactLifecycles;

API Reference

  • subAppWrapper(opts: ReactSubAppOpts)

    | option | desc | type | | ---------------- | ------------------------------------------------------------------------------------------------------------------------ | -------------- | | React | The main React object, which is generally either exposed onto the window or is available via import React from 'react' | React | | ReactDOMClient | The main ReactDOMbject, which is available via import ReactDOM from 'react-dom'. | ReactDOMClient | | rootComponent | The top level React component which will be rendered. | ReactElement | | domElementGetter | A function that is given the single-spa props and returns a DOMElement. | Function |

  • registerApps(opts: ApplicationConfig[])

    | option | desc | type | | ------- | ------------------------------------------------- | ------- | | url | A address of sub app | string | | name | The name of sub app | boolean | | library | Specify a name for the output.library of umd. | boolean | | active | Whether the sub app should be activated. | boolean |

  • launch

  • navigateTo(opts: NavigationObj)

    • NavigationObj (string | context | DOMEvent) — navigationObj must be one of the following types:
      • a url string.
      • a context / thisArg that has an href property; useful for calling singleSpaNavigate.call(anchorElement) with a reference to the anchor element or other context.
      • a DOMEvent object for a click event on a DOMElement that has an href attribute; ideal for the singleSpaNavigate use case.
  • catchError|removeCatchError(handler: ErrorHandlerFn)
    • ErrorHandlerFn (Function(error: Error)) — Must be a function. Will be called with an Error object that additionally has a message and appOrParcelName property.

DEMO

License

MIT License