Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

content collections stop updating in dev server after restarting for Astro config updates #12976

Closed
1 task
lameuler opened this issue Jan 13, 2025 · 1 comment · Fixed by #12984
Closed
1 task
Labels
- P3: minor bug An edge case that only affects very specific usage (priority) feat: content layer Related to the Content Layer feature (scope)

Comments

@lameuler
Copy link
Contributor

Astro Info

Astro                    v5.1.5
Node                     v18.20.3
System                   Linux (x64)
Package Manager          npm
Output                   static
Adapter                  none
Integrations             none

If this issue only occurs in one browser, which browser is a problem?

No response

Describe the Bug

When running the dev server, if the Astro config file is updated, it will log Configuration file updated. Restarting... and then it stops reloading data from content collection entries when they are updated.

To reproduce:

  1. start the dev server
  2. update a content collection entry. (it will correctly update and log Reloaded data from ...)
  3. update the astro config (it will restart with Configuration file updated. Restarting...)
  4. update a content collection entry again (nothing happens)

Reloading the page also does nothing. Updates to normal pages and the astro config afterwards still seem to work as normal, only content collections stop updating. Tested with both glob and file loaders.

What's the expected result?

Content collection entries should continue to update as per normal when they are updated when the dev server is running.

Link to Minimal Reproducible Example

https://stackblitz.com/edit/github-7qypgdqh

Participation

  • I am willing to submit a pull request for this issue.
@github-actions github-actions bot added the needs triage Issue needs to be triaged label Jan 13, 2025
@florian-lefebvre florian-lefebvre added - P3: minor bug An edge case that only affects very specific usage (priority) feat: content layer Related to the Content Layer feature (scope) and removed needs triage Issue needs to be triaged labels Jan 13, 2025
@ascorbic
Copy link
Contributor

This is fixed by #12984

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- P3: minor bug An edge case that only affects very specific usage (priority) feat: content layer Related to the Content Layer feature (scope)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants