Next-mdx-remote-client NPM

next-mdx-remote-client

The next-mdx-remote-client is a wrapper of @mdx-js/mdx for nextjs applications in order to load MDX content. It is a fork of next-mdx-remote.

An example application source code is at https://github.com/talatkuyuk/demo-next-mdx-remote-client.

Why `next-mdx-remote-client` ?

I started to create the next-mdx-remote-client in line with the mindset of the @mdx-js/mdx in early 2024 considering the next-mdx-remote has not been updated for a long time, and finally, a brand new package emerged.

The next-mdx-remote-client serves as a viable alternative to next-mdx-remote having more features.

Features	`next-mdx-remote`	`next-mdx-remote-client`
support MDX version 3	canary	stable
ensure internal error handling mechanism in `app` router	❌	✅
ensure internal error handling mechanism in `pages` router	❌	✅
support export-from-MDX in `app` router	❌	✅
support export-from-MDX in `pages` router	❌	✅
support import-into-MDX in `app` router	❌	✅
support import-into-MDX in `pages` router	❌	❌
get frontmatter and mutated scope in `app` router	❌	✅
get frontmatter and mutated scope in `pages` router	✅	✅
support options for disabling imports and exports in MDX	✅	✅
support passing `vfile.data` into the `scope`	❌	✅
provide utility for getting frontmatter without compiling	❌	✅
expose `MDXProvider`, `useMDXComponents` from `@mdx-js/mdx`	❌	✅
provide option for disabling parent `MDXProvider` context	❌	✅
expose the necessary types from `mdx/types`	❌	✅

!IMPORTANT You will see a lot the abbreviatons csr and rsc. Pay attention to the both are spelled backwards.\ \ csr stands for "client side rendering" which is related with pages router\ rsc stands for "react server component" which is related with app router

General considerations about development

It is ESM only package
Needs react version 18.2+, works with latest nextjs ^13.5.6 and ^14.1.3 versions (tested)
Needs node version 18.17+ as inline with nextjs does
Vitest is used instead of jest for testing
Rollup is removed for bundling
Test coverage is 100%
Type coverage is 100%
The parts client side (csr) and server side (rsc) are completely isolated from each other
Exported a small utility to get frontmatter without compiling the source
All functions take named parameters
Supports import statements and export statements in the MDX
Export statements (in the MDX) work for both app and pages router
Import statements (in the MDX) work for only app router

!IMPORTANT Imported modules in the MDX with relative path should be transpiled into javascript, before or during build process, otherwise will not work. I believe the community can find a solution to import reqular .jsx or .tsx modules into MDX. With the support of the next/mdx, it is viable to import .mdx into the MDX, but not tested yet.

Installation

This package is ESM only, requires Node.js (version 18.17+).

npm install next-mdx-remote-client

yarn add next-mdx-remote-client

!WARNING
The next-mdx-remote users may follow the migration guide.

The package's exported subpaths

The main entry point also refers to /csr subpath.

import /* */ from "next-mdx-remote-client";
import /* */ from "next-mdx-remote-client/serialize"; // for the "serialize" function
import /* */ from "next-mdx-remote-client/csr"; // related with "pages" router
import /* */ from "next-mdx-remote-client/rsc"; // related with "app" router
import /* */ from "next-mdx-remote-client/utils"; // utils

The part associated with Next.js `app` router

Go to the part associated with Next.js pages router

import { evaluate, MDXRemote } from "next-mdx-remote-client/rsc";

!TIP If you need to get the exports from MDX --> use evaluate\ If you don't need --> use MDXRemote\ \ If you need to get the frontmatter and the mutated scope --> use evaluate\ If you don't need --> use MDXRemote

The `evaluate` function

Go to the MDXRemote component

The evaluate function is used for compiling the MDX source, constructing the compiled source, getting exported information from MDX and returning MDX content to be rendered on the server side, as a react server component.

async function evaluate(props: EvaluateProps): Promise<EvaluateResult> {}

The evaluate function takes EvaluateProps and returns EvaluateResult as a promise.

Props of the evaluate function

type EvaluateProps<TScope> = {
  source: Compatible;
  options?: EvaluateOptions<TScope>;
  components?: MDXComponents;
};

Result of the evaluate function

type EvaluateResult<TFrontmatter, TScope> = {
  content: JSX.Element;
  mod: Record<string, unknown>;
  frontmatter: TFrontmatter;
  scope: TScope;
  error?: Error;
};

The evaluate has internal error handling mechanism as much as it can, in order to do so, it returns an error object if it is catched.

!CAUTION The eval of the compiled source returns a module MDXModule, and does not throw errors except syntax errors. Some errors throw during the render process which needs you to use an ErrorBoundary.

import { Suspense } from "react";
import { evaluate, type EvaluateOptions } from "next-mdx-remote-client/rsc";
import { ErrorComponent, LoadingComponent, TableOfContentComponent } from "./components";
import { components } from "./mdxComponents";
import { Frontmatter, Scope } from "./types"

export default async function MDXComponent({ source }: {source?: string}) {
  if (!source) {
    return <ErrorComponent error="The source could not found !" />;
  }

  const options: EvaluateOptions = {
    /* */
  };

  const { content, mod, frontmatter, scope, error } = await evaluate<Frontmatter, Scope>({
    source,
    options,
    components,
  });

  if (error) {
    return <ErrorComponent error={error} />;
  }

  /**
   * Use "mod", "frontmatter" and "scope" as you wish
   *
   * "mod" object is for exported information from MDX
   * "frontmatter" is available even if a MDX syntax error occurs
   * "scope" is for mutated scope if the `vfileDataIntoScope` option is used
   */

  return (
    <>
      <h1>{frontmatter.title}</h1>
      <div><em>{mod.something}</em></div>
      <TableOfContentComponent toc={scope.toc} />
      <Suspense fallback={<LoadingComponent />}>
        {content}
      </Suspense>
    </>
  );
};

If you provide the generic type parameters like await evaluate<Frontmatter, Scope>(){}, the frontmatter and the scope get the types, otherwise Record<string, unknown> by default for both.

!WARNING Pay attention to the order of the generic type parameters.\ \ The type parameters Frontmatter and Scope should extend Record<string, unknown>. You should use type instead of interface for type parameters otherwise you will receive an Error Type 'Xxxx' does not satisfy the constraint 'Record<string, unknown>'.. See this issue for more explanation.

In the above example, I assume you use remark-flexible-toc remark plugin in order to collect the headings from the MDX content, and you pass that information into the scope via vfileDataIntoScope option.

The evaluate options (`EvaluateOptions`)

All options are optional.

type EvaluateOptions<TScope> = {
  mdxOptions?: EvaluateMdxOptions;
  disableExports?: boolean;
  disableImports?: boolean;
  parseFrontmatter?: boolean;
  scope?: TScope;
  vfileDataIntoScope?: VfileDataIntoScope;
};

`mdxOptions`

It is an EvaluateMdxOptions option to be passed to the @mdx-js/mdx compiler.

import { type EvaluateOptions as OriginalEvaluateOptions } from "@mdx-js/mdx";

type EvaluateMdxOptions = Omit<
  OriginalEvaluateOptions,
  | "Fragment"
  | "jsx"
  | "jsxs"
  | "jsxDEV"
  | "useMDXComponents"
  | "providerImportSource"
  | "outputFormat"
>;

As you see, some of the options are omitted and opinionated within the package. For example the outputFormat is always function-body by default. Visit https://mdxjs.com/packages/mdx/#evaluateoptions for available mdxOptions.

const options: EvaluateOptions = {
  // ...
  mdxOptions: {
    format: "mdx",
    baseUrl: import.meta.url,
    development: true,
    remarkPlugins: [/* */],
    rehypePlugins: [/* */],
    recmaPlugins: [/* */],
    remarkRehypeOptions: {handlers: {/* */}},
    // ...
  };
};

For more information see the MDX documentation.

`disableExports`

It is a boolean option whether or not stripping the export statements out from the MDX source.

By default it is false, meaningly the export statements work as expected.

const options: EvaluateOptions = {
  disableExports: true;
};

Now, the export statements will be stripped out from the MDX.

`disableImports`

It is a boolean option whether or not stripping the import statements out from the MDX source.

By default it is false, meaningly the import statements work as expected.

const options: EvaluateOptions = {
  disableImports: true;
};

Now, the import statements will be stripped out from the MDX.

`parseFrontmatter`

It is a boolean option whether or not the frontmatter should be parsed out of the MDX.

By default it is false, meaningly the frontmatter will not be parsed and extracted.

const options: EvaluateOptions = {
  parseFrontmatter: true;
};

Now, the frontmatter part of the MDX file is parsed and extracted from the MDX source; and will be supplied into the MDX file so as you to use it within the javascript statements.

!NOTE Frontmatter is a way to identify metadata in Markdown files. Metadata can literally be anything you want it to be, but often it's used for data elements your page needs and you don't want to show directly.

---
title: "My Article"
author: "ipikuka"
---
# {frontmatter.title}

It is written by {frontmatter.author}

The package uses the vfile-matter internally to parse the frontmatter.

`scope`

It is an Record<string, unknown> option which is an arbitrary object of data which will be supplied to the MDX. For example, in cases where you want to provide template variables to the MDX, like my name is {name}, you could provide scope as { name: "ipikuka" }.

Here is another example:

const options: EvaluateOptions = {
  scope: {
    readingTime: calculateSomeHow(source)
  };
};

Now, the scope will be supplied into the MDX file so as you to use it within the statements.

# My article

read in {readingTime} min.

The variables within the expression in the MDX content should be valid javascript variable names. Therefore, each key of the scope must be a valid variable name.

My name is {name} valid expression.
My name is {my-name} is not valid expression, which will throw error

So, we can say for the scope, here:

const options: EvaluateOptions = {
  scope: {
    name: "ipikuka", // valid usage
    "my-name": "ipikuka", // is not valid and error prone for the MDX content !!!
  };
};

!TIP The scope variables can be consumed not only as property of a component, but also within the texts.

my name is {name}

<BarComponent name={name} />

`vfileDataIntoScope`

It is an union type option. It is for passing some fields of the vfile.data into the scope by mutating the scope.

!IMPORTANT
It provides referencial copy for objects and arrays. If the scope has the same key already, vfile.data overrides it.

The reason behind of this option is that the vfile.data may hold some extra information added by some remark plugins. Some fields of the vfile.data may be needed to pass into the scope so as you to use in the MDX.

type VfileDataIntoScope =
  | true // all fields from vfile.data
  | string // one specific field
  | { name: string; as: string } // one specific field but change the key as
  | Array<string | { name: string; as: string }>; // more than one field

const options: EvaluateOptions = {
  // Let's assume you use "remark-flexible-toc" plugin which composes
  // the table of content (TOC) within the 'vfile.data.toc'
  vfileDataIntoScope: "toc";
};

Now, vfile.data.toc is copied into the scope as scope["toc"], and will be supplied to the MDX via scope.

# My article

<TableOfContentComponent toc={toc} />

If you need to change the name of the field, specify it for example { name: "toc", as: "headings" }.

const options: EvaluateOptions = {
  vfileDataIntoScope: { name: "toc", as: "headings" };
};

# My article

<TableOfContentComponent headings={headings} />

If you need to pass all the fields from vfile.data, specify it as true

const options: EvaluateOptions = {
  vfileDataIntoScope: true;
};

The `MDXRemote` component

Go to the evaluate function

The MDXRemote component is used for rendering the MDX content on the server side. It is a react server component.

async function MDXRemote(props: MDXRemoteProps): Promise<JSX.Element> {}

The MDXRemote component takes MDXRemoteProps and returns JSX.Element as a promise.

Props of the MDXRemote component

type MDXRemoteProps<TScope> = {
  source: Compatible;
  options?: MDXRemoteOptions<TScope>;
  components?: MDXComponents;
  onError?: React.ComponentType<{ error: Error }>
};

The MDXRemote has internal error handling mechanism as much as it can, in order to do so, it takes onError prop in addition to evaluate function.

!CAUTION The eval of the compiled source returns a module MDXModule, and does not throw errors except syntax errors. Some errors throw during the render process which needs you to use an ErrorBoundary.

import { Suspense } from "react";
import { MDXRemote, type MDXRemoteOptions } from "next-mdx-remote-client/rsc";
import { ErrorComponent, LoadingComponent } from "./components";
import { components } from "./mdxComponents";

export default async function MDXComponent({ source }: {source?: string}) {
  if (!source) {
    return <ErrorComponent error="The source could not found !" />;
  }

  const options: MDXRemoteOptions = {
    /* */
  };

  return (
    <Suspense fallback={<LoadingComponent />}>
      <MDXRemote
        source={source}
        options={options}
        components={components}
        onError={ErrorComponent}
      />
    </Suspense>
  );
};

The MDXRemote options (`MDXRemoteOptions`)

All options are optional.

type MDXRemoteOptions<TScope> = {
  mdxOptions?: EvaluateMdxOptions;
  disableExports?: boolean;
  disableImports?: boolean;
  parseFrontmatter?: boolean;
  scope?: TScope;
  vfileDataIntoScope?: VfileDataIntoScope;
};

The details are the same with the EvaluateOptions.

The part associated with Next.js `pages` router

Go to the part associated with Next.js app router

The next-mdx-remote-client exposes serialize, hydrate and MDXClient for the pages router.

The serialize function is used on the server side in "pages" router, while as the hydrate and the MDXClient are used on the client side in "pages" router. That is why the "serialize" function is purposefully isolated considering it is intended to run on server-side.

The `serialize` function

Go to the hydrate function or the MDXClient component

import { serialize } from "next-mdx-remote-client/serialize";

The serialize function is used for compiling the MDX source, in other words, producing the compiled source from MDX source, intended to run on the server at build time.

!WARNING The serialize function is asyncronous and to be used within the getStaticProps or the getServerSideProps on the server side. (Off the record, it can be used within an useEffect as well, but this is not recommended because it is a little heavy function as having more dependencies).

async function serialize(props: SerializeProps): Promise<SerializeResult> {}

The serialize function takes SerializeProps and returns SerializeResult as a promise.

Props of the serialize function

type SerializeProps<TScope> = {
  source: Compatible;
  options?: SerializeOptions<TScope>;
};

Result of the serialize function

Either the compiledSource or the error exists, in addition to frontmatter and scope.

type SerializeResult<TFrontmatter, TScope> = 
({ compiledSource: string } | { error: Error })
& {
  frontmatter: TFrontmatter;
  scope: TScope;
};

The serialize function has internal error handling mechanism for the MDX syntax errors. The catched error is serialized via serialize-error package and attached into the serialize results, further you can deserialize the error on the client, if necessary. You don't need to implement error handling by yourself.

import { serialize, type SerializeOptions } from "next-mdx-remote-client/serialize";
import { Frontmatter, Scope } from "./types"

export async function getStaticProps() {
  const source = await getSourceSomeHow();

  if (!source) {
    return { props: {} };
  }

  const options: SerializeOptions = {
    /* */
  };

  const mdxSource = await serialize<Frontmatter, Scope>({
    source,
    options,
  });

  return {
    props: {
      mdxSource,
    },
  };
}

If you provide the generic type parameters like await serialize<Frontmatter, Scope>(){}, the frontmatter and the scope get the types, otherwise Record<string, unknown> by default for both.

!WARNING Pay attention to the order of the generic type parameters.

The nextjs will send the mdxSource (compiledSource or error + frontmatter + scope) to the client side.

On the client side, you need first to narrow the mdxSource by checking if ("error" in mdxSource) {}. It is important.

type Props = {
  mdxSource?: SerializeResult<Frontmatter, Scope>;
}

export default function Page({ mdxSource }: Props) {
  // ...

  if ("error" in mdxSource) {
    return <ErrorComponent error={mdxSource.error} />;
  }

  // ...
};

The serialize options (`SerializeOptions`)

All options are optional.

type SerializeOptions<TScope> = {
  mdxOptions?: SerializeMdxOptions;
  disableExports?: boolean;
  disableImports?: boolean;
  parseFrontmatter?: boolean;
  scope?: TScope;
  vfileDataIntoScope?: VfileDataIntoScope;
};

Except the mdxOptions, the details are the same with the EvaluateOptions.

`mdxOptions`

It is a SerializeMdxOptions option to be passed to the @mdx-js/mdx compiler.

import { type CompileOptions as OriginalCompileOptions } from "@mdx-js/mdx";

type SerializeMdxOptions = Omit<
  OriginalCompileOptions,
  "outputFormat" | "providerImportSource"
>;

const options: SerializeOptions = {
  // ...
  mdxOptions: {
    format: "mdx",
    baseUrl: import.meta.url,
    development: true,
    remarkPlugins: [/* */],
    rehypePlugins: [/* */],
    recmaPlugins: [/* */],
    remarkRehypeOptions: {handlers: {/* */}},
    // ...
  };
};

!WARNING Here I need to mention about the scope option again for the serialize.\ \ scope\ \ Actually, the serialize doesn't do so much with the scope except you provide the option vfileDataIntoScope for passing data from vfile.data into the scope. Since the scope is passed from the server to the client by nextjs, the scope must be serializable. The scope can not hold function, component , Date, undefined, Error object etc.\ \ If the scope has to have unserializable information or if you don't need or don't want to pass the scope into the serialize, you can pass it into hydrate or MDXClient directly on the client side.

The `hydrate` function

Go to the serialize function or the MDXClient component

import { hydrate } from "next-mdx-remote-client/csr";

The hydrate function is used for constructing the compiled source, getting exported information from MDX and returning MDX content to be rendered on the client side, in the browser.

function hydrate(props: HydrateProps): HydrateResult {}

The hydrate function takes HydrateProps and returns HydrateResult. The hydrate has no "options" parameter.

Props of the hydrate function

type HydrateProps = {
  compiledSource: string;
  frontmatter?: Record<string, unknown>;
  scope?: Record<string, unknown>;
  components?: MDXComponents;
  disableParentContext?: boolean;
};

The option disableParentContext is a feature of @mdx-js/mdx. If it is false, the mdx components provided by parent MDXProviders are going to be disregarded.

Result of the hydrate function

type HydrateResult = {
  content: JSX.Element;
  mod: Record<string, unknown>;
  error?: Error;
};

!TIP If you need to get the exports from MDX --> use hydrate\ If you don't need --> use MDXClient

The hydrate has internal error handling mechanism as much as it can, in order to do so, it returns an error object if it is catched.

!CAUTION The eval of the compiled source returns a module MDXModule, and does not throw errors except syntax errors. Some errors throw during the render process which needs you to use an ErrorBoundary.

import { hydrate, type SerializeResult } from "next-mdx-remote-client/csr";
import { ErrorComponent, TableOfContentComponent } from "./components";
import { components } from "./mdxComponents";
import { Frontmatter, Scope } from "./types"

type Props = {
  mdxSource?: SerializeResult<Frontmatter, Scope>;
}

export default function Page({ mdxSource }: Props) {
  if (!mdxSource) {
    return <ErrorComponent error="The source could not found !" />;
  }

  if ("error" in mdxSource) {
    return <ErrorComponent error={mdxSource.error} />;
  }

  // Now, mdxSource has {compiledSource, frontmatter, scope}

  const { content, mod, error } = hydrate({ ...mdxSource, components });

  if (error) {
    return <ErrorComponent error={error} />;
  }

  // You can use the "mod" object for exported information from the MDX as you wish

  return (
    <>
      <h1>{mdxSource.frontmatter.title}</h1>
      <div><em>{mod.something}</em></div>
      <TableOfContentComponent toc={mdxSource.scope.toc} />
      {content}
    </>
  );
};

The `MDXClient` component

Go to the serialize function or the hydrate function

import { MDXClient } from "next-mdx-remote-client/csr";

The MDXClient component is used for rendering the MDX content on the client side, in the browser.

function MDXClient(props: MDXClientProps): JSX.Element {}

The MDXClient component takes MDXClientProps and returns JSX.Element. The MDXClient has no "options" parameter like hydrate.

Props of the MDXClient component

type MDXClientProps = {
  compiledSource: string;
  frontmatter?: Record<string, unknown>;
  scope?: Record<string, unknown>;
  components?: MDXComponents;
  disableParentContext?: boolean;
  onError?: React.ComponentType<{ error: Error }>
};

The option disableParentContext is a feature of @mdx-js/mdx. If it is false, the mdx components provided by parent MDXProviders are going to be disregarded.

!TIP If you need to get the exports from MDX --> use hydrate\ If you don't need --> use MDXClient

The MDXClient has internal error handling mechanism as much as it can, in order to do so, it takes onError prop in addition to hydrate function.

!CAUTION The eval of the compiled source returns a module MDXModule, and does not throw errors except syntax errors. Some errors throw during the render process which needs you to use an ErrorBoundary.

import { MDXClient, type SerializeResult } from "next-mdx-remote-client/csr";
import { ErrorComponent, TableOfContentComponent } from "./components";
import { components } from "./mdxComponents";
import { Frontmatter, Scope } from "./types"

type Props = {
  mdxSource?: SerializeResult<Frontmatter, Scope>;
}

export default function Page({ mdxSource }: Props) {
  if (!mdxSource) {
    return <ErrorComponent error="The source could not found !" />;
  }

  if ("error" in mdxSource) {
    return <ErrorComponent error={mdxSource.error} />;
  }

  // Now, mdxSource has {compiledSource, frontmatter, scope}

  return (
    <>
      <h1>{mdxSource.frontmatter.title}</h1>
      <TableOfContentComponent toc={mdxSource.scope.toc} />
      <MDXClient
        {...mdxSource}
        components={components}
        onError={ErrorComponent}
      />
    </>
  );
};

The `hydrateLazy` function and the `MDXClientLazy` component

The next-mdx-remote-client exports additional versions, say, the hydrateLazy and the MDXClientLazy, which both have the same functionality, props, results with the hydrate and the MDXClient, correspondently.

The only difference is the hydration process takes place lazily on the browser within a window.requestIdleCallback in a useEffect. You can use hydrateLazy or MDXClientLazy in order to defer hydration of the content and immediately serve the static markup.

import { hydrateLazy, MDXClientLazy } from "next-mdx-remote-client/csr";

!NOTE Lazy hydration defers hydration of the components on the client. This is an optimization technique to improve the initial load of the application, but may introduce unexpected delays in interactivity for any dynamic content within the MDX content.\ \ This will add an additional wrapping div around the rendered MDX, which is necessary to avoid hydration mismatches during render.\ \ For further explanation about the lazy hydration see next-mdx-remote notes.

The `hydrateAsync` function and the `MDXClientAsync` component

The next-mdx-remote-client exports additional versions, say, the hydrateAsync and the MDXClientAsync.

These have additional props and options, but here, I don't want to give the details since I created these for experimental to show the import statements on the client side don't work. You can have a look at the github repository for the codes and the tests.

The main difference is that the eval of the compiled source takes place in a useEffect on the browser, since the compile source has await keyword for the import statements.

import { hydrateAsync, MDXClientAsync } from "next-mdx-remote-client/csr";

!NOTE
I believe, it is viable somehow using dynamic API if the vercel supports for a solution for the pages router via import.meta APIs. During the compilation of the MDX in the serialize, a remark/recma plugin can register the imported modules into the import.meta.url via a nextjs API (needs support of vercel) for them will be available to download/import on the client side via dynamic api. This is my imagination.

The `MDXProvider` component

The package exports the MDXProvider from @mdx-js/react, in order the developers don't need to install the @mdx-js/react.

import { MDXProvider } from "next-mdx-remote-client/csr";

The <MDXProvider /> makes the mdx components available to any <MDXClient /> or hydrate's { content } being rendered in the application, as a child status of that provider.

For example, you can wrap the whole application so as you do not need to supply the mdx components into any <MDXClient /> or hydrate's { content }.

import { MDXProvider } from 'next-mdx-remote-client/csr';
import { components } from "./mdxComponents"; 

export default function App({ Component, pageProps }) {
  return (
    <MDXProvider components={components}>
      <Component {...pageProps} />
    </MDXProvider>
  )
}

!NOTE How this happens, because the next-mdx-remote-client injects the useMdxComponents context hook from @mdx-js/react during the function construction of the compiled source, internally.
!CAUTION React server components don't support React Context, so the MDXProvider can not be used within the nextjs app router.

MDX Components

You can provide a map of custom MDX components, which is a feature of @mdx-js/mdx, in order to replace HTML tags (see the list of markdown syntax and equivalent HTML tags) with the custom components.

Typescript users can use MDXComponents from mdx/types, which is exported by this package as well.

./mdxComponents/index.ts

import { type MDXComponents } from "mdx/types";

import dynamic from "next/dynamic";
import Image from "next/image";
import Link from "next/link";

import { Typography } from "@material-ui/core";
import { motion } from 'framer-motion'

import Hello from "./Hello";
import CountButton from "./CountButton";
import BlockQuote, { default as blockquote } from "./BlockQuote";
import pre from "./pre";

export const mdxComponents: MDXComponents = {
  Hello,
  CountButton,
  Dynamic: dynamic(() => import("./dynamic")),
  Image,
  Link,
  motion,
  h2: (props: React.ComponentPropsWithoutRef<"h2">) => (
    <Typography variant="h2" {...props} />
  ),
  strong: (props: React.ComponentPropsWithoutRef<"strong">) => (
    <strong className="custom-strong" {...props} />
  ),
  em: (props: React.ComponentPropsWithoutRef<"em">) => (
    <em className="custom-em" {...props} />
  ),
  pre,
  blockquote,
  BlockQuote,
  wrapper: (props: { children: any }) => {
    return <div id="mdx-layout">{props.children}</div>;
  }
};

!NOTE The wrapper is a special key, if you want to wrap the MDX content with a HTML container element.

./data/my-article.mdx

---
title: "My Article"
author: "ipikuka"
---
_Read in {readingTime}, written by <Link href="#">**{frontmatter.author}**</Link>_

# {frontmatter.title}

## Sub heading for custom components

<Hello name={foo} />

<CountButton />

<Dynamic />

<Image src="/images/cover.png" alt="cover" width={180} height={40} />

<BlockQuote>
  I am blackquote content
</BlockQuote>

<motion.div animate={{ x: 100 }} />

## Sub heading for some markdown elements

![cover](/images/cover.png)

Here is _italic text_ and **strong text**

> I am blackquote content

Utility `getFrontmatter`

The package exports one utility, for now, which is for getting the frontmatter without compiling the source. You can get the fronmatter and the stripped source by using the getFrontmatter which employs the same frontmatter extractor vfile-matter used within the package.

import { getFrontmatter } from "next-mdx-remote-client/utils";

const { frontmatter, strippedSource } = getFrontmatter<TFrontmatter>(source);

If you provide the generic type parameter, it ensures the frontmatter gets the type, otherwise Record<string, unknown> by default.

If there is no frontmatter in the source, the frontmatter will be empty object {}.

Types

The next-mdx-remote-client is fully typed with TypeScript.

The package exports the types for server side (rsc):

EvaluateProps
EvaluateOptions
EvaluateResult
MDXRemoteProps
MDXRemoteOptions

The package exports the types for client side (csr):

HydrateProps
HydrateResult
MDXClientProps
SerializeResult

The package exports the types for the serialize function:

SerializeProps
SerializeOptions
SerializeResult

In addition, the package exports the types from mdx/types so that developers do not need to import mdx/types:

MDXComponents
MDXContent
MDXProps
MDXModule

Compatibility

The next-mdx-remote-client works with unified version 6+ ecosystem since it is compatible with MDX version 3.

Security

Allowance of the export declarations and the import declarations in the MDX, if you don't have exact control on the content, may cause vulnerabilities and harmful activities. The next-mdx-remote-client gives options for disabling them.

But, you need to use a custom recma plugin for disabiling the import expressions like await import("xyz") since the next-mdx-remote-client doesn't touch the import expressions.

Eval a string of JavaScript can be a dangerous and may cause enabling XSS attacks, which is how the next-mdx-remote-client APIs do. Please, take your own measures while passing the user input.

If there is a Content Security Policy (CSP) on the website that disallows code evaluation via eval or new Function(), it is needed to loosen that restriction in order to utilize next-mdx-remote-client, which can be done using unsafe-eval.

Some Plugins

I like to contribute the Unified / Remark / MDX ecosystem, so I recommend you to have a look my plugins.

My Remark Plugins

remark-flexible-code-titles – Remark plugin to add titles or/and containers for the code blocks with customizable properties
remark-flexible-containers – Remark plugin to add custom containers with customizable properties in markdown
remark-ins – Remark plugin to add ins element in markdown
remark-flexible-paragraphs – Remark plugin to add custom paragraphs with customizable properties in markdown
remark-flexible-markers – Remark plugin to add custom mark element with customizable properties in markdown
remark-flexible-toc – Remark plugin to expose the table of contents via Vfile.data or via an option reference
remark-mdx-remove-esm – Remark plugin to remove import and/or export statements (mdxjsEsm)

My Rehype Plugins

rehype-pre-language – Rehype plugin to add language information as a property to pre element

My Recma Plugins

recma-mdx-escape-missing-components – Recma plugin to set the default value () => null for the Components in MDX in case of missing or not provided so as not to throw an error
recma-mdx-change-props – Recma plugin to change the props parameter into the _props in the function _createMdxContent(props) {/* */} in the compiled source in order to be able to use {props.foo} like expressions. It is useful for the next-mdx-remote or next-mdx-remote-client users in nextjs applications.

License

Keywords

🟩 @mdx-js 🟩 next/mdx 🟩 next-mdx-remote 🟩 next-mdx-remote-client

markdown MDX @mdx-js/mdx nextjs next-mdx-remote next-mdx-remote-client

@babel/code-frame @mdx-js/mdx @mdx-js/react @types/mdx remark-mdx-remove-esm serialize-error vfile vfile-matter

19 days ago

1 month ago

2 months ago

2 months ago

2 months ago