Releases: contentlayerdev/contentlayer
Releases · contentlayerdev/contentlayer
0.0.31
0.0.30
0.0.29
Changes
- Fix OpenTelemetry dependencies issue (closes #30)
next-contentlayer
- Support new
next.config.mjs
ESM-style Next.js config file format
- Support new
contentlayer/source-files
- Windows: Also use posix-style file paths (i.e. use
/
instead of\
as file path separator) for user-facing file paths (e.g. in_raw
and_id
) (closes #22)
- Windows: Also use posix-style file paths (i.e. use
0.0.28
Main changes
-
Added preliminary Windows support (closes #7)
-
next-contentlayer
now ships with full MDX support out of the box (usingmdx-bundler
under the hood - closes #5). This means you no longer needmdx-bundler
as part of yourpackage.json
dependencies. Here is a simple example:import { useMDXComponent } from 'next-contentlayer/hooks' const DocPage: React.FC = ({ doc }) => { const MDXContent = useMDXComponent(doc.body.code)
-
contentlayer/source-files
added timezone support fortype: 'date'
values. (closes #9)// ... export default makeSource({ contentDirPath: 'content', documentTypes: [Doc], date: { timezone: 'America/New_York' }, })
Note:
[email protected]
requires Next.js12.x
.
Other improvements
- Allow esbuild 0.13.x in
peerDependencies
(esbuild
is still an optional dependency) - Turned "effect-ts"-related packages into optional peer dependencies. (closes #6)
- Bug fix: Calling the CLI with
--clearCache
no longer fails when no cache exists
0.0.27
0.0.26
Changes
- Generated JavaScript files in
.contentlayer
now have the.mjs
instead of the.js
extension. This shouldn't change anything for you when importing from.contentlayer
in your app (e.g. Next.js). However, if you're importing from a Node.js script, you need to supply the--experimental-json-modules
Node CLI argument (see Node.js docs).