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

mwp-application-launcher

v3.1.1

Published

MyWebPortal Application Launcher

Readme

mwp-application-launcher

All the yarn commands below are applicable to npm.

Usage

Add the module to your dependencies:

> yarn add mwp-application-launcher

Import it in your code and initialize the module:

import { init } from 'mwp-application-launcher';

const launcher = init(
  {
    url: 'https://path/to/your/api/endpoint',
    hasPermission: (permission) => { ... },
  }
);

| Option | Type | Default | Description | | --- | --- | --- | --- | | url | string | | Indicate from which url the items should be fetched. | | hasPermission | function(permission: string): boolean|Promise | | Tells whether the logged in user has the given permission. |

The hasPermission function can either

  • be synchronous and return true for allowance, false otherwise
  • be asynchronous and return a promise that will be resolved for allowance, rejected otherwise

This init function returns 2 functions:

  • renderLauncher({ container, light, ...props }) to display the items in a vertical full-height bar,
  • renderLauncherButton({ container, light, ...props}) to display a control button which opens a modal containing the items.

| Option | Type | Default | Description | | --- | --- | --- | --- | | container | string | null | A selector matching a HTML element to which the launcher will be attached. | | light | boolean | false | Whether to use the light theme instead of the dark one. | | ...props | any number of options of any type | | These options will be passed down to the launcher parent element. |

Development

Launch the development server:

yarn dev

The source folder is /src. Files with global code and functions should directly be in /src. The associated test folder is /src/__tests__. Components folders are in the form: /src/NameOfComponent. They are composed of an index.jsx and style.module.scss files, and a __tests__ folder.

Build

Build the module in /dist:

yarn build

Test

Tests are made with Jest. The following command launches all tests:

yarn test

Jest CLI arguments can be passed directly to the above command, like so: yarn test -u (updates snapshots).