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

ehi-pillar-components

v0.6.4

Published

Landing page modules built with web components

Downloads

49

Readme

eHealth Pillar Web Components

npm version PRs Welcome

Ehi-Pillar-Components is a web component library designed to help developers create the best experience for customers who shop for health insurance. Visit the eHealth style guide to learn more.

Ehi-Pillar-Components are just simple web Components, so they work in any major framework or with no framework at all. Most thanks to amazing work by the Stencil team

Using the Design System, EHI Pillar

While we do publish our design system together with these components, we recommend using our separate design project EHI Pillar

Installation

Run the following command using npm:

npm install ehi-pillar-components --save

If you prefer Yarn, use the following command instead:

yarn add ehi-pillar-components

Usage

  1. Import the CSS directly into your project if your asset packager supports it:
import 'ehi-pillar-components/dist/collection/styles/main.css';

Otherwise include the CSS in your HTML. We suggest copying the styles file into your own project, but you may also use it directly:

<link
    rel="stylesheet"
    href="https://unpkg.com/ehi-pillar-components/dist/collection/styles/main.css"
/>
  1. Include the components loader script in your project:
  • Put a script tag <script src='https://unpkg.com/ehi-pillar-components/dist/ehi-landing-components.js'></script> in the head of your index.html
  1. Then you can use the element anywhere in your template, JSX, html etc.
ReactDOM.render(
    <App>
        <Page title="Example app">
            // Example usage of web component here
            <section-simple color="blue" additional-classes="pb-0">
                <Button onClick={() => alert('Button clicked!')}>
                    Example button
                </Button>
            </section-simple>
        </Page>
    </App>,
    document.querySelector('#app')
);

Framework Integrations and Polyfills

Stencil Documentation

Methodology

We set out to make our components easy to use. Each of our components has a well-documented (and fully typed) public interface with strong, consistently-applied conventions. This way, developers don’t need to worry about the underlying implementation. Instead, they can focus on creating amazing experiences, like in our page builder built with Gutenberg blocks.

We ensure that our components are made for everyone. They are responsive to any screen or device. We also put a lot of effort into optimizing the performance of the components, so everyone can build inclusive experiences that work.

We make our components flexible enough to meet diverse needs. They present the information you pass in and give you smart callbacks when something has changed, but they don’t enforce any structure beyond that. No matter what type of experience you’re creating, you can use components as the building blocks of your product or feature.