[email protected]

Patch Changes

• [email protected]

[email protected]

Patch Changes

• 927714a: Remove dropdown from theme toggle
• d58e90a: Use await imports to import client components in Server Components
• cc1fe39: Render TOC header & footer in Server Component
• 01b23e2: Support Next.js 14
• d58e90a: Add y margins to Callout and Pre component
• Updated dependencies [2da93d8]
• Updated dependencies [01b23e2]
  • [email protected]

[email protected]

Patch Changes

• 347df32: Fix empty baseUrl unexpected behaviours
• ad7b8a8: Fully support custom root content directory paths
• 73f985a: Support rootDir API
  • [email protected]

[email protected]

Patch Changes

• 01b23e2: Support Next.js 14
• Updated dependencies [2da93d8]
• Updated dependencies [01b23e2]
  • [email protected]

[email protected]

Patch Changes

• 01b23e2: Support Next.js 14

[email protected]

Major Changes

• 6c4a782: Create PageTreeBuilder API

  The old buildPageTree function provided by 'next-docs-zeta/contentlayer' is
  now removed. Please use new API directly, or use the built-in
  createContentlayer utility instead.

  - import { buildPageTree } from 'next-docs-zeta/contentlayer'
  + import { createPageTreeBuilder } from 'next-docs-zeta/server'

Minor Changes

• 6c4a782: Improve CommonJS/ESM compatibility

  Since this release, all server utilities will be CommonJS by default unless
  they have referenced ESM modules in the code. For instance,
  next-docs-zeta/middleware is now a CommonJS file. However, some modules,
  such as next-docs-zeta/server requires ESM-only package, hence, they remain
  a ESM file.

  Notice that the extension of client-side files is now .js instead of .mjs,
  but they're still ESM.

  Why?

  After migrating to .mjs Next.js config file, some imports stopped to work.
  The built-in Next.js bundler seems can't resolve these next imports in
  external packages, causing errors when modules have imported Next.js itself
  (e.g. next/image) in the code.

  By changing client-side files extension to .js and using CommonJS for
  server-side files, this error is solved.

[email protected]

Minor Changes

• 6c4a782: Improve CommonJS/ESM compatibility

  Since this release, all server utilities will be CommonJS by default unless
  they have referenced ESM modules in the code. For instance,
  next-docs-zeta/middleware is now a CommonJS file. However, some modules,
  such as next-docs-zeta/server requires ESM-only package, hence, they remain
  a ESM file.

  Notice that the extension of client-side files is now .js instead of .mjs,
  but they're still ESM.

  Why?

  After migrating to .mjs Next.js config file, some imports stopped to work.
  The built-in Next.js bundler seems can't resolve these next imports in
  external packages, causing errors when modules have imported Next.js itself
  (e.g. next/image) in the code.

  By changing client-side files extension to .mjs and using CommonJS for
  server-side files, this error is solved.

• 6c4a782: Support Server Component usage for MDX default components

Patch Changes

• b2112e8: Improve default codeblock
• 6c4a782: Fix sidebar opening issue
• Updated dependencies [6c4a782]
• Updated dependencies [6c4a782]
  • [email protected]

[email protected]

Patch Changes

• Updated dependencies [6c4a782]
• Updated dependencies [6c4a782]
  • [email protected]

[email protected]

Minor Changes

• c36c395: Support Next Docs MDX example

[email protected]

Major Changes

• a4a8120: Update search utilities import paths.

  Search Utilities in next-docs-zeta/server is now moved to
  next-docs-zeta/search and next-docs-zeta/server-algolia.

  Client-side Changes: next-docs-zeta/search -> next-docs-zeta/search/client
next-docs-zeta/search-algolia -> next-docs-zeta/search-algolia/client

  If you're using Next Docs UI, make sure to import the correct path.

Minor Changes

• 7a0690b: Export remark-toc and remark-structure MDX plugins

Patch Changes

• 1043532: Type MDX Plugins