✔️ Deploy Preview for nuxt3-docs ready!

🔨 Explore the source changes: 3ad68ba

🔍 Inspect the deploy log: https://app.netlify.com/sites/nuxt3-docs/deploys/622f43ddf1bdd700083c1184

😎 Browse the preview: https://deploy-preview-3544--nuxt3-docs.netlify.app

Thanks for the updates @lihbr 🔥 Adding replies here as cannot reply to outdated comment anymore:

I don't have a strong opinion on it but I tend to prefer it failing fast so that developers can handle the missing case quickly (checking if the link is available before rendering) rather than thinking links are working fine and discovering months after that they never did on production. Maybe # + a warning?

Both vue-router and HTML spec do not require href attribute for a tags: (https://html.spec.whatwg.org) and there is no downside associated with it. Sometimes links really don't exist for few items in a list!

If the a eleaceholder for where a link might otherwise have been placed, if it had been relevant.

Authors may also create an A element that specifies no anchors, i.e., that doesn't specify href, name, or id. Values for these attributes may be set at a later time through scripts.

Actually, I think it makes more sense to keep it as we still want people to be able to use defineNuxtLink({ externalRelAttribute: null }) or defineNuxtLink({ externalRelAttribute: "" }) to disable the framework's default rel attribute. But let me know!

Makese sense. Then at least can we please ignore both null and undefined equally as falsy values and allow one way (empty string) to disable default value with defineNuxtLink({ externalRelAttribute: "" }) ?

Both vue-router and HTML spec do not require href attribute for a tags: (html.spec.whatwg.org) and there is no downside associated with it. Sometimes links really don't exist for few items in a list!

OK indeed wasn't thinking about that. Should it default to "#" then? (rendering href="#") or null? (rendering no href attribute)

Makes sense. Then at least can we please ignore both null and undefined equally as falsy values and allow one way (empty string) to disable default value with defineNuxtLink({ externalRelAttribute: "" }) ?

I'm fine with it, the reason I was pushing for null was that null is the Vue way or saying "don't render the attribute". Should I proceed to exclude null?

OK indeed wasn't thinking about that. Should it default to "#" then? (rendering href="#") or null? (rendering no href attribute)

null seems good idea!

I've been wondering if there's really a point to the href prop after all. It doesn't exist in Nuxt 2 and will be awkward to teach "Oh, btw, you can also use the href prop instead of the to one if that's more your jam, but if you use both, to will be preferred" 🤔 The downside is that dropping it doesn't make <NuxtLink /> a drop-in replacement for the anchor tag anymore (href has to be translate to to).

We discussed it already with @pi0 there: https://github.com/nuxt/framework/discussions/2086#discussioncomment-1683859 (and I still don't really get it)

Actually I like it now that I'm writing doc. It's nice to define <NuxtLink /> as: "a drop-in replacement for both Vue Router's <RouterLink /> component and HTML's <a> tag" ☺️

This looks like an already nice starter! What do you think is pending draft @lihbr ?

Hey there, indeed! I just synced with Daniel to fix the two last critical issues (bridge build failing + overwrite issue)

With that in mind, the <NuxtLink /> component and its documentation is quite ready IMO.

Slot API and prefetching feature can be postponed until available within the framework ☺️

Issue for prefetch support: nuxt/nuxt#13482