@next/mdx
16.4.6 · 9 Nov 2026MIT2.2M / weekRepositoryHomepagenpmAtom feed
Upgrading @next/mdx From 10.0.5 to 10.0.6
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 10
- new
- 22
- fixes
Before you upgrade
Tick each one off as you go- Breaking10.0.6
Release by release
- Breaking
Bump minimum suggested React version
- New
next: Use require.resolve instead of resolve
- New
css: Add strictPostcssConfiguration flag
- New
Add proper error when conflicting paths are detected
- Breaking
17 other lines we could not sort, mostly version bumps
- 10.0.6
Update profiling approach to cover webpack runs
- 10.0.6
Error when exporting to
staticdirectory - 10.0.6
Font optimization - remove warning message
- 10.0.6
Wrong index path revalidation timer
- 10.0.6
Minimal mode normalizing
- 10.0.6
Use webpack resolve api to resolve in externals config
- 10.0.6
Improve splitChunks config for webpack 5
- 10.0.6
Upgrade webpack 5 for empty entrypoint fix
- 10.0.6
Preserve asPath while resolving rewrites
- 10.0.6
Require only build directory to be writeable for build
75 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.