Rename useMeta to useHead

[pi0]

@atinux One issue is that useMeta shall be renamed to useHead from my POV (to be consistent with Nuxt 2 as well and avoid confusion with router meta)

Renaming meta to head, can make API consistent and familiar with Nuxt 2 and less chance of confusing with arbitrary meta definitions such as (more importantly) definePageMeta.

[atinux]

I believe we can keep useMeta as an alias + display a warning about migrating to useHead and useMeta will be removed for Nuxt 3 stable version.

[pi0]

I believe we can keep useMeta as an alias + display a warning about migrating to useHead and useMeta will be removed for Nuxt 3 stable version.

Certainly we would need backward compatibility and deprecate option and composable first :)

[atinux]

Is this something that you want to work on @danielroe ?

[atinux]

Or do you have any suggestions or things that we may missed regarding the renaming?

[antfu]

I guess also the meta configure entry in nuxt.config.js for consistency? I agree with moving to head as meta also, as meta sounds a bit too general(or ambiguous) to me.

[danielroe]

I am okay with renaming it useHead (and having head and head() options in config/components instead of meta and head()). It will reduce confusion but not entirely settle it.

[frbuceta]

This is an off-topic but related to useMeta... In nuxt@2 you could define a layout-level middleware that would affect all the pages that use it. Would this be possible in nuxt@3?

[Intevel]

Related to that, should the shortcuts be renamed then too? #13555

[atinux]

Updating the issue, I think the shortcuts should reflect the current html tag, useMetaDescription still makes sense.