chore(deps): update dependency next-mdx-remote to v4.4.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
next-mdx-remote	4.0.2 -> 4.4.1

---

Release Notes

hashicorp/next-mdx-remote (next-mdx-remote)

v4.4.1

Compare Source

What's Changed

• chore(types): remove unused imports by @​thiskevinwang in https://github.com/hashicorp/next-mdx-remote/pull/348
• fix: Make sure frontmatter types flow through to MDXRemote by @​BRKalow in https://github.com/hashicorp/next-mdx-remote/pull/351

Full Changelog: hashicorp/next-mdx-remote@v4.4.0...v4.4.1

v4.4.0

Compare Source

This release includes a few fixes for frontmatter types, as well as a way to provide a frontmatter type to serialize or compileMDX and have it propagate through to the returned frontmatter property. See the documentation for an example.

serialize:

import { serialize } from 'next-mdx-remote/serialize'

interface Frontmatter {
  title: string
  published: string
  description?: string
}

//     👇 should have type Frontmatter
const { frontmatter } = serialize<Record<string, unknown>, Frontmatter>(source)

compileMDX:

import { compileMDX } from 'next-mdx-remote/rsc'

interface Frontmatter {
  title: string
  published: string
  description?: string
}

export default async function Page({ source }) {
	//              👇 should have type Frontmatter
	const { content, frontmatter } = await compileMDX<Frontmatter>(source)

	return (
		<>
			<h1>{frontmatter.title}</h1>
			{content}
		</>
	)
}

What's Changed

• docs: fix react server components example by @​greyhere in https://github.com/hashicorp/next-mdx-remote/pull/334
• fix(rsc): do not require compiledSource in types by @​BRKalow in https://github.com/hashicorp/next-mdx-remote/pull/339
• fix: TFrontmatter type to unknown by @​RebootGG in https://github.com/hashicorp/next-mdx-remote/pull/340
• remove newline from template literal by @​chrisweb in https://github.com/hashicorp/next-mdx-remote/pull/346
• feat: Improve frontmatter types, pass generic TFrontmatter type through by @​BRKalow in https://github.com/hashicorp/next-mdx-remote/pull/342

New Contributors

• @​greyhere made their first contribution in https://github.com/hashicorp/next-mdx-remote/pull/334
• @​RebootGG made their first contribution in https://github.com/hashicorp/next-mdx-remote/pull/340
• @​chrisweb made their first contribution in https://github.com/hashicorp/next-mdx-remote/pull/346

Full Changelog: hashicorp/next-mdx-remote@v4.3.0...v4.4.0

v4.3.0: - Server Components Support (experimental)

Compare Source

next-mdx-remote now has experimental support for React Server Components! 🎉 Access the new API by importing from next-mdx-remote/rsc, and head to the documentation for usage instructions and additional examples.

import { MDXRemote } from 'next-mdx-remote/rsc'

export default async function Page() {
  const mdxSource = await getContent()

  return (
    <MDXRemote source={mdxSource} />
  )
}

Big thanks to @​timneutkens for his contribution!

---

What's Changed

• Pass components directly to compiled MDX function by @​timneutkens in https://github.com/hashicorp/next-mdx-remote/pull/330
• Add support for React Server Components by @​timneutkens in https://github.com/hashicorp/next-mdx-remote/pull/331
• chore: run tests in isolation by @​BRKalow in https://github.com/hashicorp/next-mdx-remote/pull/332
• chore: document new RSC API by @​BRKalow in https://github.com/hashicorp/next-mdx-remote/pull/333

New Contributors

• @​timneutkens made their first contribution in https://github.com/hashicorp/next-mdx-remote/pull/330

Full Changelog: hashicorp/next-mdx-remote@v4.2.1...v4.3.0

v4.2.1

Compare Source

What's Changed

• Fix: export jsx-dev-runtime in development mode by @​imtsuki in https://github.com/hashicorp/next-mdx-remote/pull/323

New Contributors

• @​imtsuki made their first contribution in https://github.com/hashicorp/next-mdx-remote/pull/323

Full Changelog: hashicorp/next-mdx-remote@v4.2.0...v4.2.1

v4.2.0

Compare Source

What's Changed

• Support serializing all VFile-compatible values by @​nwalters512 in https://github.com/hashicorp/next-mdx-remote/pull/311

New Contributors

• @​nwalters512 made their first contribution in https://github.com/hashicorp/next-mdx-remote/pull/311

Full Changelog: hashicorp/next-mdx-remote@v4.1.0...v4.2.0

v4.1.0

Compare Source

What's Changed

• chore: update reference to MDX options by @​BRKalow in https://github.com/hashicorp/next-mdx-remote/pull/280
• fix: loosen frontmatter type and make it configurable by @​joemckenney in https://github.com/hashicorp/next-mdx-remote/pull/283

New Contributors

• @​joemckenney made their first contribution in https://github.com/hashicorp/next-mdx-remote/pull/283

Full Changelog: hashicorp/next-mdx-remote@v4.0.3...v4.1.0

v4.0.3

Compare Source

What's Changed

• Improved typing of the frontmatter prop. by @​MatthijsMud in https://github.com/hashicorp/next-mdx-remote/pull/252
• fix: support both react 17 and react 18 jsx-runtime imports by @​BRKalow in https://github.com/hashicorp/next-mdx-remote/pull/267

New Contributors

• @​MatthijsMud made their first contribution in https://github.com/hashicorp/next-mdx-remote/pull/252

Full Changelog: hashicorp/next-mdx-remote@v4.0.2...v4.0.3

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
reference-marketing-website	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Mar 16, 2023 at 11:20AM (UTC)