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

mula-webapp

v2.3.34-dev.0

Published

mula. Webapp frontend. We provide a highly scalable software suite as a go to place for all merchandise activities.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

mula-dsmula-ds

Keywords

Readme

Coding Guidelines

Please read our Coding Guidelines before contributing, thanks. https://docs.google.com/document/d/1hjF8kgpYhJGFtIqKH_ajbkzLgnF83Ks-cDv-shXnaao/edit

Quick start

  1. Install Webstorm -> https://www.jetbrains.com/webstorm/download/#section=mac
  2. Install node -> https://nodejs.org/en/download/
  3. Install yarn -> https://classic.yarnpkg.com/lang/en/docs/install/#mac-stable
  4. Copy .env file to project root -> https://drive.google.com/drive/u/2/folders/1Y_MlO7349KdaxeMAJmgEjqa7aO5oexxn
    1. Use local-backend.env if you run against your localhost backend
    2. Use staging-backend.env if you run against the staging server
    3. rename to -> .env
  5. Open terminal in project root
    1. Install project -> yarn install
    2. yarn start
  6. Open Chrome and visit localhost:3000

Useful npm commands:

Command | Description

  • npm run generate | to create a new view/container or component.

Contribute to this repo:

  1. create a feature branch from development branch with the following structure
  • feature/[ticket-number]-[descriptor]
  • bug/[ticket-number]-[descriptor]
  1. test and double-check your changes before push
  2. Briefly describe what you have done in the commit messages
  3. If you are ready -> create a pull request using the development branch
  4. Move / mark your ticket for merge, also make sure the title of your ticket includes 'FE' as frontend indicator.

Features

  • Always add all new Strings on implementations to the Frontend code as well as to Localize

Documentation

Coming soon...

License

This project is licensed under to Go Mula GmbH, Copyright (c) 2021 Moritz Halfmeyer & Tobias Boertz. For more information see LICENSE.md.