Skip to content

Rollup isn't letting me build the website as a static-site #17145

Description

@SSP6904

Astro Info

Astro                    v7.0.0
Vite                     v7.3.5
Node                     v26.3.1
System                   Windows (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

I just updated Astro to version 7 after it was released and I wanted to make sure that the build command will work well with my current configuration. However, I'm getting an error message from the Rollup package that says something about the input options and that it should not be an "html file" when I'm building for server side rendering. The problem that I'm seeing with this stack trace is that I'm not actually building the website with server side rendering, and that I'm only building the website as a static-based website for GitHub Pages. Below is the exact stack trace that I'm getting based on the information that I've provided above. Note that some of the information from the stack trace will have some information hidden to prevent any sensitive information.

rollupOptions.input should not be an html file when building for SSR. Please specify a dedicated SSR entry.
  Location:
    C:\REDACTED\node_modules\vite\dist\node\chunks\config.js:33532:73
  Stack trace:
    at resolveRollupOptions (file:///C:/REDACTED/node_modules/vite/dist/node/chunks/config.js:33532:73)
    at Object.build (file:///C:/REDACTED/node_modules/vite/dist/node/chunks/config.js:33980:25)
    at Object.buildApp (file:///C:/REDACTED/node_modules/vite/dist/node/chunks/config.js:33972:26)
    at async viteBuild (file:///C:/REDACTED/node_modules/astro/dist/core/build/static-build.js:68:3)
    at async AstroBuilder.run (file:///C:/REDACTED/astro/dist/core/build/index.js:197:7)

I'm not sure if anyone else is having the same issue that I'm dealing with here, but if anyone was able to reproduce this issue, please let me know.

What's the expected result?

The website should be full compiled into the output folder that is being used from the configuration file.

Link to Minimal Reproducible Example

https://stackblitz.com/edit/github-3m7mq7mj

Participation

  • I am willing to submit a pull request for this issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions