feat: pre / post parsing hooks

[harlan-zw]

🔗 Linked issue

#2921

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

The runtime hooks from Content v2 were useful for modules to provide an integration with markdown files. For example, allowing users to provide custom frontmater keys or inferring data from the markdown body.

• Nuxt Sitemap - Nuxt Content Integration

In Content v3 these runtime hooks are moved to the build time which is a great performance win, however, we no longer have access to the parsing hooks.

This PR introduces the collection:parsedFile hook to allow modules to start integrating with v3.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[farnabaz]

Thanks for the PR

Can we also call a hook before parsing the file with raw markdown? There is also a feature request for beforeParse hook in v3 #2921

Also let's rename the hooks and add content: prefix to emphasize the hook's owner and scope.

• content:file:beforeParse (I think using :file: instead of :collection: makes more sense)
• content:file:afterParse

It is worth mentioning that the body field in v3 is minified and the tree structure is different from v2 so we might need to explain the new minified structure. (we can add this in a separate PR)

[cloudflare-workers-and-pages]

Deploying nuxt-content with    Cloudflare Pages

Latest commit:	d553630
Status:	🚫  Build failed.

View logs

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/content@2925

commit: d553630

[harlan-zw]

Thanks for the quick review! I've added beforeParse and renamed the after parse hook.

It would be nice to have the content from afterParse typed but I don't think there's a way to do that unless we introduce collection based hooks but the complexity probably isn't worth pursuing at this stage.

Let me know if you'd like anything else updated.