markdown-parser-react
v1.1.2
Published
A lightweight and configurable Markdown renderer for React and Next.js with syntax highlighting and table support.
Downloads
589
Maintainers
Readme
Markdown Parser React
Markdown Parser React is a lightweight, configurable, and easy-to-use Markdown renderer for React and Next.js with syntax highlighting support. It is built with TypeScript and can be effortlessly integrated into any React or Next.js project.
Installation
Install Markdown Parser React using npm or yarn:
bashCopy code
npm install markdown-parser-react
# or
yarn add markdown-parser-react
Usage
To use Markdown Parser React, import the Markdown
component and pass the Markdown text you want to render:
import Markdown from 'markdown-parser-react';
function MyComponent() {
const markdown = `# Hello, world!
This is **Markdown Parser React**, a *flexible* Markdown renderer.
## Syntax Highlighting
\`\`\`javascript
const message = 'Hello, world!';
console.log(message);
\`\`\``;
return <Markdown content={markdown} />;
}
Usage with Next.js
If you're using Next.js, you may encounter the "Text content does not match server-rendered HTML" error.
To avoid this issue, you can use next/dynamic
to dynamically import the Markdown
component, ensuring that it is only rendered on the client-side.
Here's how to use Markdown
with Next.js:
import dynamic from 'next/dynamic';
const Markdown = dynamic(() => import('markdown-parser-react').then((markdown) => markdown),{
ssr: false,
});
interface MyComponentProps {
content: string;
options?: {
langPrefix?: string;
};
}
export const MyComponent: React.FC<MyComponentProps> = ({ content, options }) => {
return (
<div>
<Markdown content={content} options={options} />
</div>
);
};
By using the next/dynamic
function and passing ssr as false, we ensure that the Markdown
component is only rendered on the client-side, preventing the mismatch error between server-rendered and client-rendered HTML in Next.js projects.
Parser Options
You can configure the following options for the Markdown parser:
langPrefix
Specifies the prefix to use for language classes in code blocks. The default value is 'language-'
.
const options = {
langPrefix: 'lang-',
};
Configure the Markdown parser options by passing an options
prop:
import Markdown from 'markdown-parser-react';
function MyComponent() {
const markdown = `# Hello, world!
This is **Markdown Parser React**, a *flexible* Markdown renderer.
## Syntax Highlighting
\`\`\`javascript
const message = 'Hello, world!';
console.log(message);
\`\`\``;
const parseOptions = {
langPrefix: 'lang-',
};
return <Markdown content={markdown} options={parseOptions} />;
}
Contributing
Contributions are welcome! Please read our contributing guidelines for more information.
Hire Me
If you need a freelance developer for your project, feel free to contact me at [email protected]. I have experience with React, Next.js, TypeScript, and Node.js, and I would be happy to discuss your project with you.
Why the Name Change?
We recently changed the name of the package from Markdownie to markdown-parser-react. The reason for this is that "Markdownie" is considered a slur in some English-speaking countries. We understand that language has power and we want to ensure that our package name does not cause any offense or harm to anyone. We apologize for any inconvenience this may cause and we appreciate your understanding.
Happy Coding Everyone! 🧑🏽💻