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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@ufhealth/eslint-config-wp

v1.0.0

Published

Shareable EcmaScript standard for developing UF Health WordPress projects

Readme

@ufhealth/eslint-config-wp

The shareable EcmaScript standard for developing UF Health WordPress projects.

NPM (scoped) Build Status

Key features

  • Based on @ufhealth/eslint-config-standard
  • Allows common globals exposed by WordPress in front-end views and in the editor
  • Includes WordPress-flavored React/JSX support using the wp.element pragma.

Installation & usage

yarn install @ufhealth/eslint-config-wp

Default usage

In your .eslintrc, eslint.config.js or package.json#eslint:

{
  "extends": ["@ufhealth/eslint-config-wp"]
}

By default, this configuration supports the React library bundled with WordPress, exposed as wp.element. If you're writing scripts for the block editor, or enqueueing wp-element for use on the front-end, you don't need to do anything (and we highly recommend you don't).

However, if your script isn't for the editor and you'd like to use a different version of React (or another library like Preact)...

Using a different React library

...no problem! Just change the pragma and version settings accordingly:

{
  "extends": ["@ufhealth/eslint-config-wp"],
  "settings": {
    "react": {
      "pragma": "Preact",
      "version": "8.4"
    }
  }
}

NOTE: You'll need to make sure your .babelrc pragma setting matches whatever you choose, and also make sure you import your respective library wherever you use JSX (this second step isn't required if you're using the wp.element default).