Update dependency next-contentlayer to v0.3.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
next-contentlayer	0.3.1 -> 0.3.4

---

Release Notes

contentlayerdev/contentlayer (next-contentlayer)

v0.3.4: 0.3.4

Compare Source

ℹ️ [TLDR] Many smaller bug fixes, improvements and updated dependencies

Improvements

• Added aspectRatio property to ImageFieldData for type: image fields
• Added images example
• Support for esbuild 0.18 (closes #​496)
• Upgraded various dependencies (incl. yaml package - closes #​488)
• Added MIT license to all sub packages in the Contentlayer mono repo (closes #​482)
• next-contentlayer should have contentlayer as peerDependency #​447

Bug fixes

• Fix Bug in calculation of "_raw.flattenedPath" (closes #​487)

v0.3.3: 0.3.3

Compare Source

ℹ️ [TLDR] New onSuccess callback that runs after completing a build successfully

✨ onSuccess Callback

A new callback will now be called when a successful build has completed.

The callback function receives a single argument that is an asynchronous function from which you can access data objects processed and generated by Contentlayer.

import { makeSource } from '@​contentlayer/source-files'

export default makeSource({
  onSuccess: async (importData) => {
    const { allDocuments } = await importData()
    console.log('allDocuments', allDocuments.length)
  }
})

Running a build with the above configuration would yield something like the following on the console.

allDocuments 3

Closes #​473

Better Non-Latin Character Support

Support has improved for characters in non-Latin languages. Fixes #​337.

🙌 Thanks to @​huanfe1 for help!

Other Improvements

Here are the other improvements shipped with this version.

Fix Body Field Handling for MDX

@​stefanprobst resolved the discrepancy in handling a body field in frontmatter. Now, both Markdown and MDX files behave in the same way, supporting a body field in the frontmatter. See #​451 for details.

Upgraded Dependencies

Dependencies have been upgraded to avoid warning messages. Fixes #​360.

v0.3.2: 0.3.2

Compare Source

ℹ️ [TLDR] Bug fixes for next dev, Support for next export, bug fixes and updated dependencies

Improved next-contentlayer integration

As part of 0.3.2 we've overhauled the next-contentlayer integration with the goal of making it more stable and less dependent on implementation details of Next.js. This fixes #​415 and #​416 (thanks @​kamto7).

As part of this effort (and by no longer relying on the redirects workaround) Contentlayer now also works with next export. (closes #​426)

Other Improvements

• Fix: Opentelemetry version incompatibility with next 13.2 (closes #​407 - thanks @​jgillich)
• Fix: Type resolution when using modern TypeScript module resolution (closes #​373 - thanks @​jrolfs)
• Fix: Korean file names are not supported (closes #​431 - thanks @​mi-reu)
• Fix: contentDirInclude didn't work in some cases (closes #​383 - thanks to @​teobler)

Note about state of the project

Please also take a look at #​429 to read about the current state of the project. 💜

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 (UTC)
personal	❌ Failed (Inspect)			Oct 26, 2023 8:10pm