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

@pie-players/pie-players-shared

v0.3.58

Published

Shared runtime + UI utilities for PIE players

Vulnerabilities

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

Links

Git

Maintainers

chilleniouschilleniouscarlacosteacarlacostea

Keywords

Readme

PIE Players Shared

Shared runtime utilities for the @pie-players/* player suite. This package is for framework code and host integrations that need the same loader, PIE config, security, object, i18n, or type helpers used by the player packages.

Public Exports

import { safeLocalStorageGet } from "@pie-players/pie-players-shared";
import { makeUniqueTags } from "@pie-players/pie-players-shared/pie";
import { normalizeItemPlayerStrategy } from "@pie-players/pie-players-shared";

Supported subpaths are declared in package.json:

  • @pie-players/pie-players-shared
  • @pie-players/pie-players-shared/loader-config
  • @pie-players/pie-players-shared/security
  • @pie-players/pie-players-shared/object
  • @pie-players/pie-players-shared/types
  • @pie-players/pie-players-shared/pie
  • @pie-players/pie-players-shared/pie/tag-names
  • @pie-players/pie-players-shared/loaders
  • @pie-players/pie-players-shared/server/npm-registry
  • @pie-players/pie-players-shared/i18n

Browser ESM Element Contract

The canonical producer-side contract lives with the pie-elements-ng package contract. The loader assumptions here must stay aligned with that producer surface.

The ESM element loader consumes static @pie-element/* browser entries such as dist/browser/delivery/index.js; it does not transform element packages through CDN +esm entry points. Browser ESM elements must publish exact shared runtime metadata in package.json under pie.browserSharedDependencies.

jsDelivr is the default npm CDN provider. Hosts can opt into esm.sh with loaderOptions.esmCdnProvider = "esm.sh" and loaderOptions.esmCdnUrl = "https://esm.sh". For esm.sh, PIE package artifacts are loaded from raw.esm.sh while shared browser dependencies are loaded from esm.sh. Provider names are open-ended: custom/internal providers can pass their own name when they follow the jsDelivr-compatible package-file URL layout, or pass a provider object when package artifacts and shared dependencies need different route builders.

dependencies and peerDependencies are not used as fallback runtime contracts. If multiple elements request different minor or patch versions of a shared singleton such as React, the loader chooses the highest same-major version and emits console plus instrumentation warnings. Different major versions fail the load and are also reported through console and instrumentation.

Preloaded mode means the host has already registered the expected custom element tag; it is not a separate package format. IIFE mode remains supported through the same package exports and controller compatibility shim used by legacy builders.

Related Documentation