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

@sneat/extension-contactus

v0.14.13

Published

Readme

@sneat/extension-contactus

Host-facing runtime for the contactus extension: provider wiring, routes, pages, dialogs, and concrete services. The package is public because host apps install it, but its root API is intentionally limited to provideContactus(), contactusRoutes, and membersRoutes. Extension libraries must depend on the contract or UI package instead.

App bootstrap wiring (required)

Cross-extension consumers (e.g. calendarius) inject the contactus services through the InjectionTokens defined in @sneat/extension-contactus-contract (CONTACT_SERVICE, CONTACTUS_SPACE_SERVICE, CONTACT_NAV_SERVICE, CONTACTUS_NAV_SERVICE, CONTACT_GROUP_SERVICE, CONTACT_ROLE_SERVICE, INVITE_SERVICE). The concrete implementations live here and are bound to those tokens by provideContactus().

The application (the sneat-apps super-app, which installs every @sneat/* as a real package) must call this at bootstrap:

import { provideContactus } from '@sneat/extension-contactus';

bootstrapApplication(AppComponent, {
  providers: [
    ...getStandardSneatProviders(environmentConfig),
    ...provideContactus(),
    // ...other extension providers
  ],
});

Without this, injecting a contactus token resolves to nothing at runtime. In unit tests, provide the token with a mock instead.

The composition root is the app. A library importing this runtime is rejected by both Nx project-boundary rules and the package-pattern ESLint policy.