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

2.1.5 regression: astro check fails with “astro sync command failed to generate content collection types” #6629

Closed
1 task
andersk opened this issue Mar 22, 2023 · 1 comment · Fixed by #6633 or #6811
Assignees
Labels
- P5: urgent Fix build-breaking bugs affecting most users, should be released ASAP (priority)

Comments

@andersk
Copy link
Contributor

andersk commented Mar 22, 2023

What version of astro are you using?

2.1.5

Are you using an SSR adapter? If so, which one?

None

What package manager are you using?

npm

What operating system are you using?

Linux

What browser are you using?

Firefox

Describe the Bug

astro check fails in a project using collections. It worked in 2.1.4.

This can be reproduced in the standard blog example (https://astro.new/blog).

astro check
01:33:17 PM [check] Checking files
 error   `astro sync` command failed to generate content collection types.
  Hint:
    Check your `src/content/config.*` file for typos.
  File:
    /home/projects/aonipylmz.github/node_modules/astro/dist/core/errors/errors.js:26:5
  Code:
    25 |   }
    > 26 |   setLocation(location) {
         |     ^
      27 |     this.loc = location;
      28 |   }
      29 |   setName(name) {
  Stacktrace:
Error
    at AstroError (file:///home/projects/aonipylmz.github/node_modules/astro/dist/core/errors/errors.js:26:5)
    at sync (file:///home/projects/aonipylmz.github/node_modules/astro/dist/core/sync/index.js:83:11)

Link to Minimal Reproducible Example

https://astro.new/blog

Participation

  • I am willing to submit a pull request for this issue.
@bholmesdev bholmesdev self-assigned this Mar 22, 2023
@bholmesdev bholmesdev added the - P5: urgent Fix build-breaking bugs affecting most users, should be released ASAP (priority) label Mar 22, 2023
@bholmesdev
Copy link
Contributor

bholmesdev commented Mar 22, 2023

Confirmed this was introduced by #6617, which resolved a different urgent issue 😓

Tagging @bluwy and @MoustaphaDev in case they have context on this change. Seems to be an issue resolving the astro:content virtual module. Also confirmed this issue does not occur running astro sync standalone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- P5: urgent Fix build-breaking bugs affecting most users, should be released ASAP (priority)
Projects
None yet
2 participants