fix: refresh content-index on nitro start

[Barbapapazes]

🔗 Linked issue

fix #1869

❓ 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

Here the situation:

• You start your nuxt dev server
• .nuxt is generated with a content-cache folder and a content-index.json
• You stop your nuxt dev server
• You add files in content or you modifie the architecture
• You restart your nuxt dev server but because your content-index.json is already there, index is not refreshed (https://github.com/nuxt/content/blob/main/src/runtime/server/content-index.ts#L9)

This situation also occure when you pull from remote with new files in the content folder with a stopped dev server.

Here, I remove the content-index.json file every time nitro restart to be sure that a fresh index is generated before the user restart to code.

I was thinking about using a hash but I didn't find good data to hash and this could require to check each time the user hit save. With this method (removing index when nitro start), index is re-caculated only once.

📝 Checklist

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

[codesandbox]

  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[netlify]

✅ Deploy Preview for nuxt-content canceled.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	83895b2
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt-content/deploys/640485b003a52400089c97d9

[Atinux]

Nice one, I indeed had this bug as well. I let @farnabaz review since he worked on the content index

[farnabaz]

LGTM 👍