pnpm{|npm} install mdx-editor-plugin-esm
This is a plugin for MDX Editor. It handles ESModules imports and export statements for use cases where you have to import and/or export inside of mdx files. For example if you are using MDX in astro (give link here), you might want to import components like this.
In cases like these (with es modules used inside md/mdx files), if you are using mdxeditor, out of the box, it'll show you all es modules imports and exports statements as is in the lexical editor:
After using this plugin, the ES Modules will not be shown in the lexical editor (an empty hidden div is rendered)
But you'll have access to ES Modules it in the markdown that MDXEditor emits, so that you can correctly store it in your choice of persistence. You can check by running the demo with the plugin, by cloning this repo locally and running and running pnpm{|npm} run dev and make change in the editor like this:
Screen.Recording.2024-05-14.at.1.43.07.PM.mov
From demo.tsx
import { esmMdxEditorPlugin } from 'mdx-editor-plugin-esm'
return <MDXEditor markdown={markdown} onChange={(md) => console.log('change', { md })} plugins={[...ALL_PLUGINS, esmMdxEditorPlugin()]} />This package is my first time using semantic-release and also semantic versioning. Since I didn't want to delete the package from npm, the commit messages are not matching the ethods of semantic release. For example the release 1.2.0 is a fix to make the module actually work, but it's a feat: commit to be able to do so. I will better this in the future commits.