You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the migration to MDX 1.0.0 in #137 the now deprecatedmdPlugins and hastPlugins options were not replaced with their (new named) respective
equivalents remarkPlugins and rehypePlugins. Even if the documentation states that the options will be removed in v2 and are still supported (only showing a warning in the console when still used), the defined plugins were not loaded anymore causing e.g. no more automatic generation of id attributes for headers in MDX content.
Therefore, to finish 100% of the migration, both options should be renamed.
The text was updated successfully, but these errors were encountered:
arcticicestudio
changed the title
Fix MDX remark/rehype plugin loading after 1.0 migration
Fix MDX v1 remark/rehype plugin loading after migration
May 21, 2019
During the migration to MDX 1.0.0 (1) in GH-137 the now deprecated (2)
`mdPlugins` and `hastPlugins` options were not replaced with their
(new named) respective equivalents `remarkPlugins` and `rehypePlugins`.
Even if the documentation states that the options will be removed in v2
and are still supported (only showing a warning in the console when
still used), the defined plugins were not loaded anymore causing e.g.
no more automatic generation of `id` attributes for headers in MDX
content.
Therefore, to finish 100% of the migration, both options have been
renamed.
References:
(1) https://mdxjs.com/blog/v1
(2) https://mdxjs.com/blog/v1#deprecationsGH-144
During the migration to MDX 1.0.0 in #137 the now deprecated
mdPlugins
andhastPlugins
options were not replaced with their (new named) respectiveequivalents
remarkPlugins
andrehypePlugins
. Even if the documentation states that the options will be removed in v2 and are still supported (only showing a warning in the console when still used), the defined plugins were not loaded anymore causing e.g. no more automatic generation ofid
attributes for headers in MDX content.Therefore, to finish 100% of the migration, both options should be renamed.
The text was updated successfully, but these errors were encountered: