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

es-components

v21.13.0

Published

React components built for Exchange Solutions products

Downloads

5,717

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

aabenojaaabenojajriosjriosdarrkendarrkenstevematneystevematney

Keywords

Readme

Exchange Solutions React components

Build Status npm version

Documentation and Demos

https://wtw-im.github.io/es-components/

Installation and Usage

npm install --save es-components

es-components comes optimized for tree shaking. If your build tool does not support tree shaking please direct your imports towards es-components/lib. You may use either direct file paths or destructure from the index file.

// use this to keep the size of your bundles light
import Component from 'es-components/lib/path/to/component';
// or
import { Component } from 'es-components/lib';

Using The UMD Bundle

Because ES Components needs a reference to document.body on startup, you must either include the defer attribute, or place the <script> tag somwhere within the body of your html page. Here we're showing it using the defer attribute.

<!DOCTYPE html>
<head>
  <meta charset="UTF-8" />
  <title>My ES Components Site</title>
  <!-- These fonts are used by es-components -->
  <link
    rel="stylesheet"
    href="https://app.viabenefits.com/static/cdn/es-assets/icons.css"
  />
  <link
    rel="stylesheet"
    href="https://app.viabenefits.com/static/cdn/es-assets/source-sans-pro.css"
  />
  <!-- You must include React, ReactDOM, PropTypes and Styled Components. ES Components depends on those packages. -->
  <script
    crossorigin
    src="https://app.viabenefits.com/static/third-party/react@16/umd/react.production.min.js"
  ></script>
  <script
    crossorigin
    src="https://app.viabenefits.com/static/third-party/react-dom@16/umd/react-dom.production.min.js"
  ></script>
  <script
    crossorigin
    src="https://app.viabenefits.com/static/third-party/prop-types@15/prop-types.js"
  ></script>
  <script
    crossorigin
    src="https://app.viabenefits.com/static/third-party/styled-components/dist/styled-components.min.js"
  ></script>
  <script
    crossorigin
    defer
    src="https://app.viabenefits.com/static/third-party/es-components/bundle/main.min.js"
  ></script>
</head>

<body>
  <!-- My ES Components Site Body -->
</body>

Jest

es-components uses ResizeObserver, but if you're using jsdom, it doesn't come with it. You can set up jest to work with es-components by using build-utils/jest in your setupFilesAfterEnv configuration. Eg:

// jest.config.js

module.exports = {
  // other jest config
  setupFilesAfterEnv: [
    'es-components/build-utils/jest'
    // others...
  ]
};