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

pf-3-to-4

v1.0.1

Published

Codemods for v4 breaking change release 2020.07

Downloads

4

Readme

pf-3-to-4

CLI utility to help ease products transitioning to our new major @patternfly/react-core 4.0.0 release.

Goals

  • We want to minimize code changes and respect existing code
  • We only want to make safe modifications
    • Don't touch code that we aren't sure is PatternFly

redallen rationale

  • Most consumers are using JSX
    • When they're using React.createElement or React.cloneElement that introduces unsafe complications

Design

  • Use a JSX parser that leaves formatting alone as much as possible
  • Add basic ESM import parsing to make sure we're only modifying PatternFly <Button>s

Development

This is what @redallen does to develop a rule:

  1. Copy a rule at lib/rules/*
  2. Add it to .eslintrc.json
  3. Copy a test at test/rules/*
  4. Put code into an AST explorer like https://astexplorer.net/ . Add code to "failing" version of test.
  5. Write rule targeting specific AST node. Confirm AST node exists in lib/rules/ast-node-types.d.ts.
  6. Amend test/test.tsx with code that requires fixing.
  7. Develop fixer while testing it with npm run test -- --fix