https://npmx.dev/ yet is a new frontend for the npm registry, created by people close to the vite community. It's officially launching tomorrow, but I have been using it for the past few weeks and it's so much better than npmjs.org.

Some cool things:

• it has auto-generated docs from the TS types, for example https://npmx.dev/package-docs/@babel%2Ftypes/v/8.0.0-rc.2. If we add JSDoc descriptions, they will show up there too. It might be worth getting good enough JSDoc that we can stop, for example, maintaining the @babel/types docs on our website. We'll probably need to work with npmx.dev folks to help them better support our needs for it to happen though.
• it lets users click on a little drop down to see the install command with all the various package manager CLIs, rather than showing only install instructions for npm. This aligns with what we did on our website, to give "fair treatment" to all the clients.
• the code viewer is much nicer than the npm one, and you can link to files in it: https://npmx.dev/package-code/@babel/core/v/7.29.0 (and the browser back button works!)

npmx.dev still has multiple bugs, but there is almost nothing that npmjs.com does better then it so I think it's worth changing our links.

I did not update two links:

• babel/.github/workflows/issue-triage.yml

  Line 102 in cd22e3a

  for example, https://www.npmjs.com/package/@babel/types?activeTab=versions is the URL for `@babel/types`

  
  npmx.dev does not have a page to show all the versions of a package. I think this is the only feature that npmjs.com does better than npmx.dev: we should keep the npmjs.com URL there. I opened Linkable package page to show list of versions npmx-dev/npmx.dev#1846 to track implementing this on the npmx.dev side.
• the scripts/ensure-package-exists.ts script. I think npmx.dev is going to also have better package admin management than npm, but I have not explored yet how it works. It will require adding a dependency to the monorepo so that npmx.dev can talk locally to it to do admin stuff (rather than sending your password to their server), but that package has not been published yet.

This PR also slightly reorganizes the badges in our main readme, removing the GitPod and v6 downloads ones.