Remove all references to @mdx-js/react #80870
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Remove all references to
@mdx-js/react
. One occurrence remains in the lockfile due to an indirect dependency.Why?
@mdx-js/react
is actively harmful for Next.js users.@mdx-js/react
uses React context. React context can’t be used in server components. As a result, users who have@mdx-js/react
inside theirnode_modules
get confusing errors.Removing
@mdx-js/react
from all documentation, tests, and optional peer dependencies, has no drawbacks. Removing@mdx-js/react
as anext-mdx-import-source
alias, fixes the confusing errors.Users who insist on using
@mdx-js/react
, can still do this by explicitly specifying theproviderImportSource
option.How?
Search for
@mdx-js/react
, and remove all occurences it.