rsnext/packages/next-mdx
2020-03-23 18:46:48 -04:00
..
index.js Improve linting rules to catch more errors (#9374) 2019-11-10 19:24:53 -08:00
license.md Move next-mdx from zeit/next-plugins to zeit/next.js (#6443) 2019-03-04 18:02:45 +01:00
package.json v9.3.2-canary.3 2020-03-23 18:46:48 -04:00
readme.md docs: remove --save from npm install; avoid system-ui (#10252) 2020-01-27 08:35:12 -05:00

Next.js + MDX

Use MDX with Next.js

Installation

npm install @next/mdx @mdx-js/loader

or

yarn add @next/mdx @mdx-js/loader

Usage

Create a next.config.js in your project

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

Optionally you can provide MDX options:

// next.config.js
const withMDX = require('@next/mdx')({
  options: {
    mdPlugins: [],
    hastPlugins: [],
  },
})
module.exports = withMDX()

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

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

Optionally you can match other file extensions for MDX compilation, by default only .mdx is supported

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

Top level .mdx pages

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

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

Typescript

Follow this guide from the MDX docs.