fix(deps): bump next-mdx-remote from 2.1.4 to 3.0.1

[dependabot]

Bumps next-mdx-remote from 2.1.4 to 3.0.1.

Release notes

Sourced from next-mdx-remote's releases.

3.0.0

⚠️ This is a BREAKING RELEASE and will require manual changes ⚠️

This release includes a full rewrite of the internals of next-mdx-remote to make it faster, lighter-weight, and behave more predictably! The migration should be fairly quick for most use-cases, but it will require some manual changes. Thanks to our community for testing out this release and providing early feedback. ❤️

Major changes

• renderToString has been replaced with serialize
• hydrate has been replaced with <MDXRemote />
• Removed provider configuration, React context usage should now work without additional effort
• Content will now hydrate immediately by default
• Dropped support for IE11 by default

Migrating to v3

As of v3, usage of next-mdx-remote is slightly different. renderToString has been replaced with serialize, and hydrate has been removed in favor of the <MDXRemote /> component.

Under the hood, v3 is more efficient and we've fixed a number of long-standing caveats with the way it was implemented. Most users should notice improved performance across the board!

First step:

// npm
npm install next-mdx-remote@latest
// yarn
yarn add next-mdx-remote@latest

Here's what the diff looks like to migrate a simple implementation:

- import renderToString from 'next-mdx-remote/render-to-string'
+ import { serialize } from 'next-mdx-remote/serialize'
- import hydrate from 'next-mdx-remote/hydrate'
+ import { MDXRemote } from 'next-mdx-remote'
import Test from '../components/test'
const components = { Test }
export default function TestPage({ source }) {

const content = hydrate(source, { components })
return (
<div className="wrapper">

 {content}





 &lt;MDXRemote {...source} components={components} /&gt;

</div>
)
}
</tr></table>

... (truncated)

Commits

• 3d1c707 3.0.1
• ccf97cf fix: usage of fragments in MDX (#128)
• 907fa0f 3.0.0
• bf000ef next-mdx-remote v3 (#121)
• 7eaa346 Bump y18n from 4.0.0 to 4.0.1 (#117)
• 3444136 Bump elliptic from 6.5.3 to 6.5.4 (#112)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/imadatyatalah/portfolio-boilerplate-nextjs/J1xT2rNEveKcFMgEcvy8Gsz29de5
✅ Preview: Failed

[Deployment for 7e2d4af failed]

[imadatyatalah]

Thanks dependabot

[dependabot]

Superseded by #32.