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

@emintech/example-package

v0.8.0

Published

Reference frontend package for the EminCore ecosystem demonstrating package lifecycle management, registry integrations, package architecture, and frontend development best practices.

Readme

Example Package Frontend

Example Package Frontend is a reference frontend package for the EminCore ecosystem.

It demonstrates package structure, registry integrations, package lifecycle management, and frontend development best practices while also serving as a test fixture for package manager validation.

Purpose

This package is intentionally simple and is used for:

  • Frontend package installation testing
  • Frontend package update testing
  • Frontend package uninstallation testing
  • Registry management testing
  • Asset registration testing
  • Marketplace package development examples
  • Custom package development examples
  • Learning the EminCore frontend architecture
  • Demonstrating frontend package development best practices
  • Providing a reference implementation for frontend package developers

Additionally, this package demonstrates:

  • Page Registry integration examples
  • Widget Registry integration examples
  • Provider Registry integration examples
  • Frontend package structure recommendations
  • Ecosystem integration patterns
  • Package lifecycle integration patterns

Architecture

The package follows the recommended frontend package structure for the EminCore ecosystem.

It demonstrates:

  • Package entrypoint registration (emincore.register.ts)
  • Registry-based page registration
  • Registry-based widget registration
  • Registry-based provider registration
  • Integration separation and organization
  • Provider-based application bootstrapping
  • Runtime extensibility patterns

Versions

Each version introduces small, controlled changes to simulate real-world package evolution and validate package manager behavior.

Examples include:

  • New page registrations
  • New widget registrations
  • New provider registrations
  • Component updates
  • Asset updates
  • Registry updates
  • Package structure changes
  • Frontend integration changes

The goal is to validate installation, update, rollback, and uninstallation scenarios across multiple package versions.

Notes

This package is not intended for production use.

Although intentionally simple, its structure reflects the recommended approach for developing frontend packages within the EminCore ecosystem.

It serves as:

  • A package manager test fixture
  • A frontend architecture example
  • A frontend package development reference
  • A best practices showcase for EminCore package developers