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

@wix/site-service-pages

v1.0.2

Published

Provides all site pages (with popup flag), the current page, and the main page.

Readme

@wix/site-service-pages

Provides all site pages (with popup flag), the current page, and the main page.

Install

yarn add @wix/site-service-pages

Usage

import { PagesDefinition } from '@wix/site-service-pages/definition'
import { PagesService } from '@wix/site-service-pages/implementations'

createServicesMap().addService(PagesDefinition, PagesService, config)

const service = servicesManager.getService(PagesDefinition)
// service.pages        ← Record<string, Page>
// service.mainPage     ← Page (resolved by provider, stored as-is)
// service.currentPage  ← Page (resolved by provider, stored as-is)

API

| Member | Type | Throws when | Description | |---|---|---|---| | pages | Record<string, Page> | never | All pages with id stamped from map key. | | mainPage | Page | never | The site's main/home page as provided. | | currentPage | Page | never | The currently active page as provided. | | _updateConfig | (Partial<IPagesServiceConfig>) => void | never | Replace-on-write per field. Re-stamps id on pages update. |

Configuration

IPagesServiceConfig:

type IPagesServiceConfig = {
    /** id-as-key map; values omit `id` (P3). Service stamps id at write time (P16). */
    pages: Record<string, PageConfig>
    /** Provider resolves and passes the full main page object. */
    mainPage: Page
    /** Provider resolves and passes the full current page object. */
    currentPage: Page
}

type PageConfig = {
    title: string
    path: string
    parentPageId?: string
    popup: boolean
}

type Page = PageConfig & { id: string }

The provider is responsible for resolving which page is mainPage / currentPage before injecting config. The service stores them as independent signals and does no internal lookup.

Reactivity

This service is a thin signal wrapper over @wix/services-definitions/core-services/signals. All three properties are signal-backed; wrap reads in effect / computed to react to changes. Signals are not exposed directly.