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
Currently, Nuxt MDC uses rehype-external-links to handle external links. However, it might be worth reconsidering its usage.
Proposal 1: Direct handling in the ProseA component
I wonder if the use of rehype-external-links could be shifted directly to the ProseA component. This would:
Centralize link management in the final rendering component.
Offer more control and flexibility to developers who want to customize the behavior of external links.
Proposal 2: Add default attributes consistent with NuxtLink
If rehype-external-links is retained, it would be helpful to include the rel="noopener noreferrer" attributes by default, aligning with the behavior of NuxtLink.
These attributes improve security by preventing referrer leaks and access to parent pages via window.opener.
It ensures a unified experience for links generated by Nuxt, whether internal or external.
Benefits
Strengthen consistency between internal and external links in Nuxt MDC.
Simplify configuration for users who want a safe and standard behavior for external links.
Enable a more intuitive and centralized management of specific link behaviors.
Thank you for your work on Nuxt MDC! 😊
The text was updated successfully, but these errors were encountered:
Description
Currently, Nuxt MDC uses
rehype-external-links
to handle external links. However, it might be worth reconsidering its usage.Proposal 1: Direct handling in the
ProseA
componentI wonder if the use of
rehype-external-links
could be shifted directly to theProseA
component. This would:Proposal 2: Add default attributes consistent with
NuxtLink
If
rehype-external-links
is retained, it would be helpful to include therel="noopener noreferrer"
attributes by default, aligning with the behavior ofNuxtLink
.window.opener
.Benefits
Thank you for your work on Nuxt MDC! 😊
The text was updated successfully, but these errors were encountered: