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

pie-catalog-client

v2.3.1

Published

The client code for the catalog

Downloads

139

Readme

catalog client

The client side app to render a pie element in a catalog view

Usage

This package contains a set of custom elements that make up the ui. Below is a of notable elements:

name | description | api ---------|---------- | --- catalog-container | This contains a header/footer and a slot for contents | isLoading(true|false) catalog-entry | displays tabs, one with a demo and one with information | set element catalog-demo | renders a demo of the element | set controllers, config, markup

bootstrapping

For your convenience there are some modules that you can import that will bootstrap related elements for you:

  • src/bootstrap/repo - all the elements for a repo view
  • src/bootstrap/index - all the elements for an index page view
  • src/bootstrap/org - all the elements for an org view

All these export common which is a promise that will resolve once the main elements have been defined. In repo we use webpack's require.ensure to load additional logic asynchronously, keeping the initial load small. When this logic is loaded the elementsDefined promise will resolve.

See the example for a demo.

Browser support

  • Chrome
  • Safari +10.1

polyfills

These elements provide no additional browser support (with the exception of shadycss, which is baked into the source). You are expected to load the polyfills you need yourself.

Demo

npm install 
cd demo
../node_modules/.bin/webpack-dev-server --hot --inline

# then go to localhost:8080

Test

Warning: Tests are currently failing - selenium is failing to boot chrome. It may be that we have to move away from web-component-tester.

You'll need to bower install Polymer/web-component-tester --save to install wct bower deps.

npm install -g web-component-tester

Once it's released we can just add it to the devDependencies, and update the npm test cmd.

Release

npm run release