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

@skivy71/demo-wallet

v1.0.17

Published

Demo Wallet published as web component

Downloads

2

Readme

Demo Wallet

Introduction

A repo designed to develop and publish web components.

Installation

yarn

(recommended over npm, as the package.json contains resolutions to dependancy vulnerabilties)

Structure

(The default folders)

./src -
    ./main.svelte (build entry point)

./dist - 
    ./ (...build artifacts are placed here)

./html - 
    ./local.html (for local component testing / loading)
    ./public.html (file for public component loading / unpkg, jsdelivr)

./scripts - 
    ./ (package.json scripts)

Unpkg

This service allows you to consume the published npm module directly in the browser.

You will need to publish your package via npm publish

It allows: -

a). @org/demo-wallet - latest release (via package.json, main or module)

b). @org/[email protected] - specifc version 1.0.3

c). @org/demo-wallet@^1.0.3 - 1.0.3 or later

Jsdelivr

This service allows you to consume directly from github, but has some caveats: -

a). The need to specify the actual file you wish to use (as opposed to the package.json definition)

b). Github releases have to be defined manually (either via github.com or their cli).

c). Package.json becomes largely redundant (version and file).

Usage

Use the root component file to define the entry point and code in accordance with the library api (svelte in this case).

yarn run serve - web server, using the ./html/local.html file

yarn run serve:public - as above, but uses .html/public.html

yarn run build - builds artifacts, saved in ./dist, as per rollup config (esm, umd, minified versions).

Note

The above web servers watch ./dist (and the respective *.html file), so changes (i.e. build) will trigger a hot reload.

By default, local.html serves on 1234 and public.html on 1235, so you there's no confusion as to which environment is being tested.