Astro Info
Astro v6.1.10
Node v24.14.1
System macOS (arm64)
Package Manager pnpm
Output static
Adapter none
Integrations none
If this issue only occurs in one browser, which browser is a problem?
No response
Describe the Bug
A newly created Astro project fails to start with the default generated configuration. Running pnpm run dev immediately exits during config validation with:
[config] Astro found issue(s) with your configuration:
! integrations: Required
The project was generated by the Astro CLI and the config file contains the default config:
export default defineConfig({});
No integrations were added or modified manually. The dev server only starts after explicitly adding an empty integrations array:
export default defineConfig({
integrations: [],
});
What's the expected result?
A fresh Astro CLI project should run with the generated default config, or Astro should treat missing integrations as equivalent to an empty array.
Link to Minimal Reproducible Example
https://github.com/rodrigosdev/astro-blog-tutorial
Participation
Astro Info
If this issue only occurs in one browser, which browser is a problem?
No response
Describe the Bug
A newly created Astro project fails to start with the default generated configuration. Running pnpm run dev immediately exits during config validation with:
The project was generated by the Astro CLI and the config file contains the default config:
No integrations were added or modified manually. The dev server only starts after explicitly adding an empty integrations array:
What's the expected result?
A fresh Astro CLI project should run with the generated default config, or Astro should treat missing integrations as equivalent to an empty array.
Link to Minimal Reproducible Example
https://github.com/rodrigosdev/astro-blog-tutorial
Participation