@benjamincanac it seems that content module isn't allowing me to add the link text with http and have had to make this pr to fix broken markdown links. Are you aware of this behaviour. this pr fixes it but I am sure it was working properly before. If you need me to submit an issue to content let me know.

@danielroe can you check this pr please. tests are failing in CI again but working locally only on this pr. Error from cypress is timeout rather than a link error like we had before so it might be just cypress going mad. Did re-run jobs and no luck. Any ideas?

cypress: https://github.com/nuxt/nuxtjs.org/pull/1194/checks?check_run_id=1762235229

As promised ✨

Its also on your blog article, and maybe at many more pages 😓

hi thanks for reporting. yes it seems to be an issue. trying to figure out whats causing it. Possibly a markdown issue in nuxt-edge as seems to have broken all links. @pi0 shall I transfer this issue to nuxt, fix all links manually or revert to earlier version to see if it fixes the markdown?

Hi @debs-obrien. Issue seems also happening with 2.14.12. Made nuxt/content#737 with minimal reproduction for this.

Ok cool. Thanks @pi0. I had reached out to Ben first but he told me it wasn't a content thing. Perhaps the error has been there longer than we thought 🤷‍♀️

There is a blackhole in node_modules 🤣 Regression is probably one of sub dependencies updated with yarn.lock.

If you know a commit that was fine, we may fallback yarn lock and compare what changed since

You're right, @pi0, it is a regression in one of sub dependencies, more specifically in micromark-extension-gfm-autolink-literal @ 0.5.5. I've linked details in your issue.