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

recma-mdx-change-props

v1.1.1

Published

This recma plugin changes the 'props' parameter into '_props' in the function '_createMdxContent'; and makes appropriate changes in order to be able to use the expression containing for example {props.foo} in the mdx.

Downloads

58

Readme

recma-mdx-change-props

NPM version NPM downloads Build codecov type-coverage typescript License

[!WARNING]
The recma-mdx-change-props is useful for next-mdx-remote or next-mdx-remote-client users in nextjs applications.

This package is a unified (recma) plugin to provide using the expression like {props.foo} in a MDX document.

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?

This plugin is useful if you want to use expressions like {props.foo} in a MDX document.

Thanks to the plugin, you can pass "props" object in the scope variable in next-mdx-remote or next-mdx-remote-client projects.

const scope = {
  props: {
    foo: "foofoo",
    baz: "bazbaz"
  }
}

<MDXRemote scope={scope} /* ... */ />

The recma-mdx-change-props changes the props parameter into _props in the function _createMdxContent in the compiled source; and makes appropriate changes in order to do so. Without recma-mdx-change-props, there will be a confliction caused by "props" in the function _createMdxContent(props){} and the expression like {props.foo} in a MDX document will not work.

Installation

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

npm install recma-mdx-change-props

or

yarn add recma-mdx-change-props

Usage

Say we have the following file, example.mdx,

# Hi {props.foo}
      
<Test name={props.baz} />

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

import { read } from "to-vfile";
import { compile } from "@mdx-js/mdx";
import recmaMdxChangeProps from "recma-mdx-change-props";

main();

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

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

  return String(compiledSource);
}

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

function _createMdxContent(_props) {
  const _components = {
    h1: "h1",
    ..._props.components
  }, {Test} = _components;
  // ...
  return _jsxs(_Fragment, {
    children: [_jsxs(_components.h1, {
      children: ["Hi ", props.foo]
    }), "\\n", _jsx(Test, {
      name: props.baz
    })]
  });
}

And, this provides us to pass an object containing the props key during function construction of the compiled source.

const scope = {
  title: "My Article",
  props: {
    foo: "foofoo",
    bar: "barbar",
  }
}

Without the recma-mdx-change-props, the statements props.foo and props.baz will be undefined during function construction.

function _createMdxContent(props) {
  const _components = {
    h1: "h1",
    ...props.components
  }, {Test} = _components;
  // ...
  return _jsxs(_Fragment, {
    children: [_jsxs(_components.h1, {
      children: ["Hi ", props.foo]
    }), "\\n", _jsx(Test, {
      name: props.baz
    })]
  });
}

Options

All options are optional, and implemented as for being more flexible in case of need to change the names.

export type ChangePropsOptions = {
  funcName?: string; // default is "_createMdxContent" which the plugin looks for
  propName?: string; // default is "props" which the plugin looks for
  propAs?: string; // default is "_props" which the plugin converts into
};

The options are self-explainotary, so that is why no need to represent more example here.

use(recmaMdxChangeProps, {propAs: "__props__"} as ChangePropsOptions);

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 ChangePropsOptions.

Compatibility

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

Security

Use of recma-mdx-change-props 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

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

MIT License © ipikuka

Keywords

🟩 unified 🟩 recma 🟩 recma plugin 🟩 esast 🟩 MDX 🟩 recma mdx