The beautiful docs framework for Next.js. Alternative to Nextra
MIT License
Bot releases are visible (Hide)
Published by github-actions[bot] 12 months ago
Published by github-actions[bot] 12 months ago
Published by github-actions[bot] 12 months ago
Published by github-actions[bot] 12 months ago
Published by github-actions[bot] almost 1 year ago
Published by github-actions[bot] almost 1 year ago
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
Published by github-actions[bot] almost 1 year ago
Published by github-actions[bot] almost 1 year ago
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'
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.
Published by github-actions[bot] about 1 year ago
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.
Updated dependencies [1043532]
Updated dependencies [7a0690b]
Updated dependencies [a4a8120]
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
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.
Published by fuma-nama about 1 year ago
Published by fuma-nama about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by fuma-nama about 1 year ago
Published by fuma-nama about 1 year ago
Published by fuma-nama about 1 year ago
Published by fuma-nama about 1 year ago
Published by fuma-nama about 1 year ago