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

@oviirup/next-mdx

v15.2.4

Published

Use MDX with Next.js

Downloads

2

Readme

@oviirup/next-mdx

Use MDX with Next.js

[!NOTE] This is a slightly modified version of the original @next/mdx package

Installation

For usage with the app directory see the section below.

npm install @oviirup/next-mdx

Usage

Update your a next.config.js in your project

// next.config.js
const withMDX = require('@oviirup/next-mdx')();
module.exports = withMDX();

Optionally you can provide MDX plugins:

// next.config.js
const withMDX = require('@oviirup/next-mdx')({
  options: {
    remarkPlugins: [],
    rehypePlugins: [],
  },
});
module.exports = withMDX();

Optionally you can add your custom Next.js configuration as parameter

// next.config.js
const withMDX = require('@oviirup/next-mdx')();
module.exports = withMDX({
  // your custom next config ...
  webpack(config, options) {
    return config;
  },
});

By default MDX will only match and compile MDX files with the .mdx extension. However, it can also be optionally configured to handle markdown files with the .md extension, as shown below:

// next.config.js
const withMDX = require('@oviirup/next-mdx')({
  extension: /\.(md|mdx)$/,
});
module.exports = withMDX();

In addition, MDX can be customized with compiler options, see the mdx documentation for details on supported options.

Top level .mdx pages

Define the pageExtensions option to have Next.js handle .md and .mdx files in the pages or app directory as pages:

// next.config.js
const withMDX = require('@oviirup/next-mdx')({
  extension: /\.mdx?$/,
});
module.exports = withMDX({
  pageExtensions: ['js', 'jsx', 'ts', 'tsx', 'md', 'mdx'],
});

Custom Components

The mdx-components file is required specially in case if you are using app directory. By default the plugin looks for the file at mdx-components.js or src/mdx-components.js, or its typescript equivalent, but you can specify your own path.

Create an mdx-components.js file at the root of your project with the following contents:

// This file is required to use @next/mdx in the `app` directory.
export function useMDXComponents(components) {
  return components;
  // Allows customizing built-in components, e.g. to add styling.
  // return {
  //   h1: ({ children }) => <h1 style={{ fontSize: "100px" }}>{children}</h1>,
  //   ...components,
  // }
}

Create a next.config.js in your project

// next.config.js
const withMDX = require('@next/mdx')({
  // Provide path to custom mdx-components path (optional)
  components: 'src/components/mdx',
  // Optionally provide remark and rehype plugins
  options: {
    // If you use remark-gfm, you'll need to use next.config.mjs
    // as the package is ESM only
    // https://github.com/remarkjs/remark-gfm#install
    remarkPlugins: [],
    rehypePlugins: [],
  },
});

/** @type {import('next').NextConfig} */
const nextConfig = {
  // Configure pageExtensions to include md and mdx
  pageExtensions: ['ts', 'tsx', 'js', 'jsx', 'md', 'mdx'],
  // Optionally, add any other Next.js config below
  reactStrictMode: true,
};

// Merge MDX config with Next.js config
module.exports = withMDX(nextConfig);

TypeScript

Follow this guide from the MDX docs.