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

@elastic/eslint-plugin-eui

v0.0.3

Published

This package contains an eslint plugin that enforces some default rules for using EUI.

Downloads

128,117

Vulnerabilities

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

Links

Git

Maintainers

lenegadewolllenegadewollcbishopewccbishopewccindy_ccindy_casnyder-elasticasnyder-elasticlgestclgestcpatryk.kopycinskipatryk.kopycinskibanerjeesoham004banerjeesoham004legregolegregobradtimmermanbradtimmermandevcorpiodevcorpioyan.savitskiyan.savitskijeramysoucyjeramysoucytkajtochtkajtochjohnwcambrajohnwcambracolleen.mcginniscolleen.mcginnisscottybollingerscottybollingerkyrsplkyrsplphoey1phoey1verogoverogobreehallbreehalltrevorpiercetrevorpierceglitteringkatieglitteringkatiejen-huangjen-huangdelvedordelvedorlukasolsonlukasolsonccowanccowanjbudzjbudzthomasneirynckthomasneirynckweltenwortweltenwortpugnascotiapugnascotiazinckiwizinckiwibrandon.kobelbrandon.kobelnreesenreesemgreaumgreaujonahbulljonahbulljarpyjarpyleathekdleathekdlukeelmerslukeelmersddillingerddillingerjoshdoverjoshdoverjasonstoltzjasonstoltzbamiehbamiehmarkov00markov00joshmockjoshmockvignesh.shanmugamvignesh.shanmugamwatsonwatsonrhodesjasonrhodesjasonjmlrtjmlrtmattkimemattkimeconstancecchenconstancecchenafoucretafoucretnickpeihlnickpeihlaxwaxwmisticmisticelasticmachineelasticmachinegtbackgtbackpickypgpickypgtrentmtrentmandrewvc-elasticandrewvc-elasticjorge.sanzjorge.sanzstratoulastratoulankammahnkammahstreamichstreamichnickofthymenickofthymechloerukachloeruka

Keywords

Readme

@elastic/eslint-plugin-eui

This package contains an eslint plugin that enforces some default rules for using EUI.

Setup

  1. install @elastic/eslint-plugin-eui as a dev dependency
  2. extend plugin:@elastic/eui/recommended in your eslint config

Rules

@elastic/eui/href-or-on-click

<EuiButton /> should either be a button or a link, for a11y purposes. When given an href the button behaves as a link, otherwise an onClick handler is expected and it will behave as a button.

In some cases it makes sense to disable this rule locally, such as when cmd+click should open the link in a new tab, but a standard click should use the history.pushState() API to change the URL without triggering a full page load.

Publishing

This package is published separately from the rest of EUI, as required by eslint. The code is not transpiled, so make sure to use require() statements rather than import, and once the code is updated run:

  1. npm version patch|minor|major
  2. commit version bump
  3. npm publish in this directory
  4. push the version bump upstream