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
Is your feature request related to a problem? Please describe
Currently, developing and testing custom remark plugins locally is unnecessarily complicated due to two main issues:
Module Resolution Conflict: When passing a resolved remark plugin, the module loader bypasses the local version and assumes I have a package installed and tries to resolve it by the key 🙄.
Forced Package Resolution: Even after working around the initial import check, the compiled mdc-imports.mjs file still attempts to resolve plugins via the key specified in the Nuxt Content config, ignoring locally provided implementations.
Technical demonstration of the issue:
Describe the solution you'd like
We need the ability to use local remark plugins without the requirement to:
JessicaSachs
changed the title
Ability to pass in an unpublish remark plugin as a function to nuxt.config.ts
Ability to pass in an unpublished remark plugin as a function to nuxt.config.ts
Nov 5, 2024
Is your feature request related to a problem? Please describe
Currently, developing and testing custom remark plugins locally is unnecessarily complicated due to two main issues:
Module Resolution Conflict: When passing a resolved remark plugin, the module loader bypasses the local version and assumes I have a package installed and tries to resolve it by the key 🙄.
Forced Package Resolution: Even after working around the initial
import
check, the compiledmdc-imports.mjs
file still attempts to resolve plugins via the key specified in the Nuxt Content config, ignoring locally provided implementations.Technical demonstration of the issue:
Describe the solution you'd like
We need the ability to use local remark plugins without the requirement to:
Ideal implementation would look like this:
Additional context
This feature would greatly improve the developer experience for:
The text was updated successfully, but these errors were encountered: