@next/mdx 13.4.6-canary.2 → 13.4.6-canary.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/readme.md +4 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@next/mdx",
3
- "version": "13.4.6-canary.2",
3
+ "version": "13.4.6-canary.3",
4
4
  "main": "index.js",
5
5
  "license": "MIT",
6
6
  "repository": {
package/readme.md CHANGED
@@ -51,7 +51,8 @@ module.exports = withMDX({
51
51
  })
52
52
  ```
53
53
 
54
- Optionally you can match other file extensions for MDX compilation, by default only `.mdx` is supported
54
+ By default MDX will only match and compile MDX files with the `.mdx` extension.
55
+ However, it can also be optionally configured to handle markdown files with the `.md` extension, as shown below:
55
56
 
56
57
  ```js
57
58
  // next.config.js
@@ -61,6 +62,8 @@ const withMDX = require('@next/mdx')({
61
62
  module.exports = withMDX()
62
63
  ```
63
64
 
65
+ In addition, MDX can be customized with compiler options, see the [mdx documentation](https://mdxjs.com/packages/mdx/#compilefile-options) for details on supported options.
66
+
64
67
  ## Top level .mdx pages
65
68
 
66
69
  Define the `pageExtensions` option to have Next.js handle `.md` and `.mdx` files in the `pages` directory as pages: