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

recma-mdx-import-media

v1.2.4

Published

Recma plugin to turn media relative paths into import declarations for both markdown and html syntax in MDX

Readme

A robust Next.js newsletter Next.js Weekly is sponsoring me 💖 NextjsWeekly banner

Become a sponsor 🚀

If you find recma-mdx-import-media useful in your projects, consider supporting my work.
Your sponsorship means a lot 💖

My sponsors are going to be featured here and on my sponsor wall.

A warm thanks 🙌 to @ErfanEbrahimnia, @recepkyk, and @LSeaburg for the support!

Thank you for supporting open source! 🙌

recma-mdx-import-media

npm version npm downloads publish to npm code-coverage type-coverage typescript license

This package is a unified (recma) plugin that turns media relative paths into import declarations for both markdown and html syntax in MDX

unified is a project that transforms content with abstract syntax trees (ASTs) using the new parser micromark. recma adds support for producing a javascript code by transforming esast which stands for Ecma Script Abstract Syntax Tree (AST) that is used in production of compiled source for the MDX.

When should I use this?

You can use recma-mdx-import-media if you want to include media/asset with relative path using markdown syntax or html syntax in MDX, without providing an import statement, such as:

![alt](./image.png)

<img src="./image.png" alt="alt" />

![alt](../blog-assets/image.png)

<img src="../blog-assets/image.png" alt="alt" />

Because, recma-mdx-import-media creates import statements and assigns an identifier into proper element in the compiled source.

recma-mdx-import-media only processes relative paths (starting with ./ or ../ or direct file name); leaving protocol-like patterns (like http://), root-relative URLs (like /pathname), and absolute paths (file:///) unchanged.

You might run into issues because bundlers like Webpack and Vite don't natively recognize these references (.png, .jpeg etc.), they only handle imports. recma-mdx-import-media bridges that gap by converting media relative references into import declarations in the compiled MDX source, ensuring bundlers can process them correctly, for both markdown and HTML syntax.

The list of the tags and attributes that recma-mdx-import-media process

  • img --> src, srcset
  • video --> src, poster
  • audio --> src
  • source --> src, srcset
  • embed --> src
  • track --> src
  • input[type="image"] --> src
  • script --> src

recma-mdx-import-media supports meta information (#hash and ?querystring) on the asset path.

During process, the meta information in the relative path is stripped out in the import statement.

In order you process the meta information for further process, it is added as a property into the asset as data-meta for src and poster attributes, but it preserved in srcset instead of passing it to data-meta.

Installation

This package is suitable for ESM only. In Node.js (version 18+), install with npm:

npm install recma-mdx-import-media

or

yarn add recma-mdx-import-media

Usage

Say we have the following file, example.mdx,

![alt](./image.png)

<img src="../../image.png" alt="alt" />

And our module, example.js, looks as follows:

import { read } from "to-vfile";
import { compile } from "@mdx-js/mdx";
import recmaMdxImportMedia from "recma-mdx-import-media";

main();

async function main() {
  const source = await read("example.mdx");

  const compiledSource = await compile(source, {
    recmaPlugins: [recmaMdxImportMedia],
  });

  return String(compiledSource);
}

Now, running node example.js produces the compiled source like below:

// ...
+ import imagepng$recmamdximport from "./image.png";
+ import imagepng_1$recmamdximport from "../../image.png";
function _createMdxContent(props) {
  const _components = {
    img: "img",
    p: "p",
    ...props.components
  };
  return _jsxs(_Fragment, {
    children: [_jsx(_components.p, {
      children: _jsx(_components.img, {
-        src: "./image.png",
+        src: imagepng$recmamdximport,
        alt: "alt"
      })
    }), "\\n", _jsx("img", {
-      src: "../../image.png",
+      src: imagepng_1$recmamdximport,
      alt: "alt"
    })]
  });
}
// ...

This is roughly equivalent with:

import imagepng$recmamdximport from "./image.png";
import imagepng_1$recmamdximport from "../../image.png";

export default function MDXContent() {
  return (
    <p>
      <img alt="alt" src={imagepng$recmamdximport} />
      <img alt="alt" src={imagepng_1$recmamdximport} />
    </p>
  )
}

If you want to resolve the relative paths (starts with ./ or ../) of the assets for further process, you are recommended to use recma-mdx-change-imports.

Options

All options are optional and have default values.

export type ImportMediaOptions = {
  excludeSyntax?: Array<"markdown" | "html">; // default is empty array []
};

excludeSyntax

It is an array option to exlude markdown or html syntax or both. The option are self-explainotary.

use(recmaMdxImportMedia, { excludeSyntax: ["html"] } as ImportMediaOptions);

Now, <img /> like html syntax will be excluded.

use(recmaMdxImportMedia, { excludeSyntax: ["markdown"] } as ImportMediaOptions);

Now, ![]()) like markdown syntax will be excluded.

use(recmaMdxImportMedia, { excludeSyntax: ["html", "markdown"] } as ImportMediaOptions);

Now, both html and markdown syntax will be excluded. The plugin becomes effectless.

Syntax tree

This plugin only modifies the ESAST (Ecma Script Abstract Syntax Tree) as explained.

Types

This package is fully typed with TypeScript. The plugin options is exported as ImportMediaOptions.

Compatibility

This plugin works with unified version 6+. It is compatible with mdx version 3+.

Security

Use of recma-mdx-import-media does not involve user content so there are no openings for cross-site scripting (XSS) attacks.

My Plugins

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

My Remark Plugins

My Rehype Plugins

  • rehype-pre-language – Rehype plugin to add language information as a property to pre element
  • rehype-highlight-code-lines – Rehype plugin to add line numbers to code blocks and allow highlighting of desired code lines
  • rehype-code-meta – Rehype plugin to copy code.data.meta to code.properties.metastring
  • rehype-image-toolkit – Rehype plugin to enhance Markdown image syntax ![]() and Markdown/MDX media elements (<img>, <audio>, <video>) by auto-linking bracketed or parenthesized image URLs, wrapping them in <figure> with optional captions, unwrapping images/videos/audio from paragraph, parsing directives in title for styling and adding attributes, and dynamically converting images into <video> or <audio> elements based on file extension.

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.
  • recma-mdx-change-imports – Recma plugin to convert import declarations for assets and media with relative links into variable declarations with string URLs, enabling direct asset URL resolution in compiled MDX.
  • recma-mdx-import-media – Recma plugin to turn media relative paths into import declarations for both markdown and html syntax in MDX.
  • recma-mdx-import-react – Recma plugin to ensure getting React instance from the arguments and to make the runtime props {React, jsx, jsxs, jsxDev, Fragment} is available in the dynamically imported components in the compiled source of MDX.
  • recma-mdx-html-override – Recma plugin to allow selected raw HTML elements to be overridden via MDX components.
  • recma-mdx-interpolate – Recma plugin to enable interpolation of identifiers wrapped in curly braces within the alt, src, href, and title attributes of markdown link and image syntax in MDX.

License

MIT License © ipikuka