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

@wdft/gvm-sdk

v0.1.3

Published

get via msg sdk - gvm.js

Readme

gvm.js

WDFT - We Do Fintech
GetViaMsg SDK and WebComponents

Showcase of gvm.js web-component

Entrypoints / modes

The package ships three integration layers — pick the one that fits, they don't interfere with each other:

| Entrypoint | Mode | Use it when | | --- | --- | --- | | @wdft/gvm-sdk (npm) | raw SDK — programmatic getViaMsg(), no DOM | you build your own UI and control everything | | dist/gvm.js | declarative — auto-init, reads data-gvm-* + inline <template> | you hand-write the paywall markup | | dist/gvm-overlay.js | config-driven — fetches a JSON config, injects data-gvm-*, boots gvm.js | you want a zero-config, centrally-managed paywall |

  • gvm.js and gvm-overlay.js are isolated ES modules served from a CDN (or bundled).
  • Loading gvm-overlay.js (instead of gvm.js) is the overlay signal — no flag needed; config and admin-editor URLs are derived from data-gvm-env + data-gvm-tenant (see gvm-overlay docs).
  • The admin editor (gvm-admin.js) is loaded lazily on ?gvm_admin=1 by gvm-overlay.js only.

Custom API endpoint

Beside data-gvm-env (demo|local|dev|qa|prod), you can point at an arbitrary API URL with data-gvm-endpoint (absolute URL). When set, the real environment is used regardless of data-gvm-env.

<body data-gvm data-gvm-env="demo" data-gvm-endpoint="https://api.example.com" ...>

gvm-overlay.js (config-driven layer)

gvm-overlay.js is a zero-config layer on top of gvm.js: it fetches a JSON config and applies prices/paywalls to content marked with data-gvm-reference. Loading gvm-overlay.js (instead of gvm.js) is the overlay signal — integration is a one-liner, with the attributes on the <script> tag:

<script type="module"
        src="https://esm.sh/@wdft/gvm-sdk@latest/gvm-overlay.js"
        data-gvm-tenant="your_tenant"
        data-gvm-env="dev"></script>
<div data-gvm-reference="my-article">…paywalled content…</div>

data-gvm-config, data-gvm-admin-src and data-gvm-admin-api are optional overrides. Templates (paywall + payment) come from the config (templates.paywall / templates.payment) — the overlay ships no built-in markup. Docs: gvm-overlay. Backend/admin editor: gvm-sdk-admin.

Changelog

See changelog

More & Contact

Read more about our service GetViaMsg at https://getviamsg.com