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

wcm

v3.4.0

Published

Web Components Manager, a tool to version web components

Downloads

139

Readme

Web Components Manager

npm prettier

Description

This project is an attempt to unify how vanilla Web Components are bundled, distributed, imported, and generally managed as a whole. We're targeting HTML first Web Components, and currently support TypeScript and JavaScript (potentially more languages will be supported in future releases).

WCM gives you an incredible level of control over which dependencies are imported by your application, and at what versions.

Legacy Mode

Not every browser supports Service Workers in all cases, some restrict this feature in private tabs, some are just plain old. If you need to support these cases, WCM can run in legacy mode, allowing the browser to import your dependencies as if WCM wasn't there at all, but does require an extra build step when deploying.

Installation

You can install the CLI from NPM, it should be saved as a development dependency, but you could install it globally if required.

npm i wcm -D

To configure WCM in your project, you have a number of options thanks to the use of cosmiconfig internally. You can choose between any of the following.

  1. A wcm property in your projects package.json
  2. A .wcmrc file written in either JSON or YAML format
  3. A wcm.config.js file exporting a JS object

Development

Running the following will install this projects dependencies, and build WCM for the first time.

npm ci

After you've installed the projects dependencies, you can build this project by running the following command.

npm run prepare