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

web-component-shards

v1.1.4

Published

Build an app with shared dependencies!

Downloads

5

Readme

web-component-shards

Builds a multi-page app with shared dependencies.

Definitions

Endpoint

An HTML file containing the complete dependencies and implementation for one or more pages of a web application. An example E-Commerce app could have three endpoints, shop.html, orders.html, and cart.html. Each of these files must be stored in the same directory structure, with some shared dependencies(at least polymer.html).

Usage

wcs <options>

  • -h, --help Print usage.
  • -b, --bowerdir string Bower components directory. Defaults to 'bower_components'
  • -r, --root string Root directory against which URLs in inputs are resolved. If not specified, then the current working directory is used.
  • -e, --endpoints string[] Application endpoints to vulcanize.
  • -i, --shared_import string Name of the programatically created common dependency file. Defaults to 'shared.html'
  • -s, --sharing_threshold number Number of endpoints an import must be found in to be added to 'shared_import'. For example, 2 will include all imports found in at least 2 endpoints, and 1 will include all dependencies of any endpoint. Defaults to 2.
  • -d, --dest_dir string Destination for vulcanized application. Defaults to 'dist/'.
  • -w, --workdir string Temporary directory for holding in-process files. DANGER: this directory will be deleted upon tool success. Defaults to 'tmp/'