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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@monetized/widgets

v0.0.5

Published

A set of custom elements to prompt your users to buy the premium content at Monetized, and for validating their entitlement tokens.

Downloads

5

Readme

@monetized/widgets

A set of custom elements to prompt your users to buy the premium content at Monetized, and for validating their entitlement tokens.

<monetized-link-riser>

Adds a pop-under to:

  1. Check if there's an entitlement token available set in page URL.
  2. If it's set, ensure it's a valid token.
  3. If token is invalid or doesn't exist, find the corresponding page at https://www.monetized.link and prompt user to get access there.

Usage

<!doctype html>
<html lang="en">
	<head>
		<meta name="viewport" content="width=device-width, initial-scale=1.0" />
		<!-- You can use npm CDNs like unpkg to import the custom element -->
		<script
			type="module"
			src="https://unpkg.com/@monetized/widgets/monetized-link-riser.js"
		></script>
		<!-- Or, self-host it -->
		<script type="module" src="monetized-link-riser.js"></script>
	</head>
	<body>
		<p>Some content on your website</p>

		<!-- Add the riser widget  -->
		<monetized-link-riser></monetized-link-riser>
	</body>
</html>

Advanced Usage

You can use a custom name for this component too.

<script type="module">
	import { MonetizedLinkRiser } from 'https://unpkg.com/@monetized/widgets/monetized-link-riser.js';
	customElements.define('some-custom-name', MonetizedLinkRiser);
</script>

<some-custom-name></some-custom-name>

Pass the strict attribute for strict checking - ensures the token corresponds to only the page monetized at https://www.monetized.link

<monetized-link-riser strict></monetized-link-riser>
<!-- Note that this attribute doesn't expect any value. To unset, remove the attribute. -->

@monetized/api

Use Monetized's public API to validate entitlement of tokens, and directing users to correct pages where they can buy your link.

npm install @monetized/api

Available methods

import {
	getPage,
	findPage,
	verifyToken,
	verifyTokenStrict,
} from '@monetized/api';

getPage

Get a page by page ID

GET https://www.monetized.link/api/content/info/:pageId

findPage

Find a page by monetized URL

GET https://www.monetized.link/api/content/find?q={monetizedPageUrl}&publication={optional-publication-id}

verifyToken

Check whether given token is valid. Validates corresponds to public key at .well-known/jwks.json.

verifyTokenStrict

Same as above, but also ensures the token corresponds to given URL/page-id.