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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@matixinc/gatsby-plugin-azure-external-image

v1.0.1

Published

The first approch was to use the extract-image-paths plugin that parses an MDX node and add extra fields on the node itself that are resolved at runtime. The problem with this approach comes when we try to synchronize images to azure using the newly add

Readme

The first approch was to use the extract-image-paths plugin that parses an MDX node and add extra fields on the node itself that are resolved at runtime. The problem with this approach comes when we try to synchronize images to azure using the newly added fields. They are not available in createNodes since they have to be resolved first and to be resolved, we need to be able to query the node but this is not possible in createNode extension point.

Next approach.

Create a new type of Node - MatixNode and make a 1-1 relationship between Mdx and Matix

  1. The new node will be created using a plugin that will parse mdx and output the content in the MatixNode
  2. A source plugin will be created as well in order to synchronize the content to azure, it will create a MatixAzureNode which will create a reference to a FileNode
  3. A relationship will be made between MatixNode, MatixAzureNode and Mdx
  4. A resolver will be made to expose the resulting FileNode in the Mdx schema to facilita querying this data.