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

@vermilion/web-components

v0.2.2

Published

A library of reusable web components for rapid development

Downloads

2

Readme

Vermilion Design + Digital Web Components

This repository is a working library of web components built on the Polymer / LitElement platforms.

Demo and list of components and usage:

Demo and Component Documentation

Usage

npm i @vermilion/{package-name-not-published-yet}

In your Javascript:

import { ComponentName } from '@vermilion/{package-name-not-published-yet}';

  ... 

customElements.define('component-name', ComponentName);
  /** 
    * your component name must include a hyphen so the HTML parser in your browser knows this is a custom element.
  **/

In your HTML:

<component-name
  other="properties"
  passed="like this"
>
  Slot Data passed here
</component-name>

Contributing | Development

  1. Clone this repo
  2. $ cd vermilion-web-components
  3. $ npm install

Build Tasks:

To run a development build and watch the Javascript files only:

$ npm start

To develop for the browser at localhost:1234 on the file at /demo/index.html

$ npm run dev

To build only the Javascript files for production use:

$ npm run build

To build the documentation and demo HTML files for production

$ npm run build-demo

To build everything for production:

$ npm run package

Development

  1. Take a look at /template.js for a boilerplate component class. This can serve as a scaffolding to how we are writing these components.
  2. All new web components must be single, top-level files inside the src folder.
  3. Prefix your example components with "vm-" in the examples.
  4. When your component is ready for the browser, import it to /src/index.js/ and add it to the exported object as a named export.
  5. run one of the build taks above. Most likely npm run dev.

Publishing

  1. When you're ready to publish a component, first make sure that you've done everything you can to make it flexible and accessible (including tabindex and keyboard events);

  2. Add an example to the /demo/index.html file with the following template:

  <section class="component" id="{{component-name}}">
    <h2>{{component-name}}</h2>

    <div class="container">

      <vm-{{component-name}}></vm-{{component-name}}>

      <h3>Usage:</h3>
        <pre>
          HTML:  
            <code class="language-html">
              <!--  your example markup here. -->
            </code>

          JavaScript:
            <code class="language-javascript">
              import { {{ComponentName}} } from './dist/index';
                ...
              customElements.define('vm-{{component-name}}', {{ComponentName}});
            </code>
        </pre>
    </div>
  </section>
  1. $ npm run build
  2. Submit a Pull Request for all new Components.