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

@withmarsha/embed

v1.0.0

Published

Marsha Web Receptionist embed loader (script-tag widget).

Vulnerabilities

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

Links

Maintainers

marsha.appmarsha.app

Keywords

Readme

@withmarsha/embed

Loader del widget de la Recepcionista web de Marsha, distribuido por npm para poder servirlo vía CDN (unpkg).

La fuente única del loader es public/embed.js (en la raíz del repo). Este paquete no tiene su propia copia: el script prepublishOnly copia public/embed.js aquí justo antes de publicar, así que nunca hay drift.

Una sola vez: cuenta y login

  1. Tener una cuenta npm con acceso al scope @withmarsha (crear la org en npmjs.com; gratis para paquetes públicos).
  2. Iniciar sesión en la máquina:
    npm login          # abre el navegador para autenticar
npm whoami         # confirma que estás logueado
    La sesión queda guardada; no hay que repetirlo en cada publicación.

Publicar una versión nueva

  1. Edita el loader en public/embed.js (no aquí).
  2. Sube la versión en packages/embed/package.json (semver):
    • parche (1.0.0 → 1.0.1) para fixes,
    • minor (1.0.0 → 1.1.0) para cambios compatibles,
    • major (1.0.0 → 2.0.0) para cambios que rompen el snippet del cliente.
  3. Publica:
    cd packages/embed
npm publish
    prepublishOnly copia public/embed.js y publishConfig.access: "public" ya lo deja como paquete público.

unpkg lo sirve automáticamente (no se "sube" nada a unpkg):

https://unpkg.com/@withmarsha/[email protected]/embed.js

Comprobar qué se va a publicar sin publicar:

cp ../../public/embed.js ./embed.js && npm pack --dry-run && rm embed.js

Snippet que pega el cliente

<script async
  src="https://unpkg.com/@withmarsha/embed@^1.0.0/embed.js"
  data-receptionist="recp_xxx"></script>
  • ^1.0.0 = el cliente recibe la última 1.x automáticamente; un cambio que rompa exige publicar 2.0.0 y que el cliente actualice el rango a mano.
  • data-receptionist = publicId de una Recepcionista web en estado published, con el dominio del cliente en su allowedDomains.
  • data-origin = opcional, solo para apuntar a un backend que no sea prod (dev/staging/preview). Por defecto el loader usa https://withmarsha.com.

Alternativa: self-host

public/embed.js también se sirve desde el propio dominio (https://withmarsha.com/embed.js). Ese canal se auto-actualiza con cada deploy sin publicar nada. unpkg solo aporta versionado pineado por cliente.