fix: refresh content-index on nitro start #1947
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
fix #1869
β Type of change
π Description
Here the situation:
.nuxt
is generated with acontent-cache
folder and acontent-index.json
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