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

mdx-variables

v1.0.3

Published

A package for reading variables from .mdx files

Downloads

21

Readme

mdx-variables

This package enables you to read/extract variables that have been defined inside .mdx files. Find out more about the use cases and how to use this package here.


Getting Started

Install the package

npm install mdx-variables

Using the package

  1. Create an MDX file and define your variables

(mdx-example/pages/my-page.mdx)

const metadata = {
    author: 'Reece Charsville',
    date: new Date('2021-06-09T12:00:00.000Z'),
    tags: ['hello', 'world']
}


### This is my markdownX file
I can create my markdown file here using the metadata variable we defined.

<TagsComponent tags={metadata.tags} />
    
<Footer author={metadata.author} date={metadata.date} />
  1. Now we can create our React component and extract the metadata

(mdx-example/blog-index.tsx)

import * as React from "react";
import { ReadVarFromMDX } from "mdx-variables";

type MDXTypes = {
    tags: Array<string>;
    author: string;
    date: Date;
}

const BlogIndex: React.FC = ({ children }): JSX.Element => {
    const [meta, setMeta] = React.useState<MDXTypes>();
    const [metaFromFile, setMetaFromFile] = React.useState<MDXTypes>();
    
    React.useEffect(() => {
        // This example uses a string value of the filename as the source
        const meta: MDXTypes = ReadVarFromMDX<MDXTypes>('metadata', 'pages', 'my-page.mdx');
        setMeta(meta);

        // This example uses an .mdx file buffer as the source
        const source: Buffer = fs.readFileSync('C:/mdx-example/pages/my-page.mdx');
        const metaFile: MDXTypes = ReadVarFromMDX<MDXTypes>('metadata', 'pages', source);
        setMetaFromFile(metaFile);
    }, []);
    
    return (
        <>
            <TagsComponent tags={meta?.tags} />
            <div>
                {children}
            </div>
            <div>{metaFile?.author} - {metaFile?.date}</div>
        </>
    );
};
export default BlogIndex;

API

ReadVarFromMDX(variable, path, source)

| Parameter | Type | Description | | --- | --- | --- | | variable | string | The name of the variable that is defined inside the markdown file. Variable definitions must be defined using const or let. | | path | string | The path from the project root to the directory where the markdown file is located. | | source | string | Buffer | Either a string value representing the name of the markdown file including the .mdx extension "filename.mdx" or a file buffer for the mdx file.


NOTE

If you are going to use this package with Next.js then you may want to use superjson. Next.js by default does not parse JS Date objects into component props. This means that variables inside the .mdx files containing JS Date objects can not be read/extracted without using superjson. You can read more about this Next.js limitation here.

To use superjson with Next.js

  1. Install the following packages:
npm install babel-loader babel-plugin-superjson-next superjson
  1. Create or edit the .babelrc file and add the following:
{
  presets: ["next/babel"],
  plugins: [
    "superjson-next"
  ]
}