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

wmk-rich-text

v4.0.10

Published

WMK RichText Component on Typescript

Readme

wmk-rich-text

RichText class

new RichText(node: RichTextQuery)
  1. Consumes Contentful RichText data and converts it to format compatible with component.

  2. Relocates embedded reference data to within the requisite content nodes inside each rich text's blocks JSON object.

Sample GraphQL RichText Query

const sampleQuery = graphql`
  {
    contentfulPost {
      content {
        raw
        references {
          __typename
          ... on ContentfulLink {
            contentful_id
            title
            url
          }
          ... on ContentfulBlog {
            contentful_id
            image {
              gatsbyImageData
              title
              file {
                url
                contentType
              }
              description
            }
            path
            title
          }
        }
      }
    }
  }
`;

The __typename field is important. It helps identify what references data is being called during block processing.

The contentful_id field is important, and is required to match references within Rich Text raw data.

Failure to include those queried fields will result in error messages.

RichTextReact

<RichTextReact content={RichText} options={richTextOptions} />

The content prop must be instantiated RichText, and the options prop is now required and must be in @contentful/rich-text-types Options format.

EmbeddedBlock

    [BLOCKS.EMBEDDED_ENTRY]: (node: RichTextNode) => {
      const entry = new EmbeddedBlock(node, CompHash);
      return entry.render();
    }

Intended to be used within richTextOptions on the [BLOCKS.EMBEDDED_ENTRY] key, this component will help associate custom JSX with queried embedded blocks in Contentful Rich Text data.

Node will be of type RichTextNode, which is an extension of Contentful's rich text types but also includes reference data. NOTE: since there is only one reference per block, the property name has been changed to reflect that: reference instead of references.

Pass the queried node along with a Component hash object. The hash object must have keys that correspond to each block's __typename.

Example Component Hash Object

Each associated component will get reference data passed as props. If the component can use those props outright, it can be a simple key: Component relationship.

If the associated component needs to pre-process the given reference props, the best was is to return the Component in an inline functional component like with the ContentfulBlog example below.

const CompHash = {
  ContentfulLink: LinkBlockComponent,
  ContentfulBlog: ({
    image,
    title,
    path
  }: {
    image: ContentfulImageQuery;
    title: string;
    path: string;
  }) => <BlogBlockComponent image={new Img(image)} title={title} path={path} />
};