Astro Info
Astro v6.1.0
Vite v7.3.1
Node v24.14.0
System Linux (x64)
Package Manager npm
Output static
Adapter @astrojs/netlify (v7.0.5)
Integrations none
If this issue only occurs in one browser, which browser is a problem?
All
Describe the Bug
Since upgrading to Astro 6, Astro Actions no longer work with @astrojs/netlify adapter when output is set to 'static'.
The build and dev server fail with:
[ERROR] [astro:actions] An unhandled error occurred while running the "astro:routes:resolved" hook
[ActionsWithoutServerOutputError] A server is required to create callable backend functions. To deploy routes to a server, add an adapter to your Astro config and configure your route for on-demand rendering
Changing output to 'server' resolves the issue — however, this was not required in Astro 5, where Actions worked fine with the default static output mode and the Netlify adapter.
This appears to be a breaking change / regression.
I had a similar issue with the netlify adapter: when using server:defer there was a problem on the netlify server with server islands (#16049 ).
The fix was a simple change in order of execution by the netlify adapter. I suspect a similar issue here.
What's the expected result?
The output "static" config should suffice to use Astro Actions with the netlify adapter.
Link to Minimal Reproducible Example
https://github.com/PanRoR/astro-server-island-netlify
Participation
Astro Info
If this issue only occurs in one browser, which browser is a problem?
All
Describe the Bug
Since upgrading to Astro 6, Astro Actions no longer work with @astrojs/netlify adapter when
outputis set to'static'.The build and dev server fail with:
[ERROR] [astro:actions] An unhandled error occurred while running the "astro:routes:resolved" hook
[ActionsWithoutServerOutputError] A server is required to create callable backend functions. To deploy routes to a server, add an adapter to your Astro config and configure your route for on-demand rendering
Changing
outputto'server'resolves the issue — however, this was not required in Astro 5, where Actions worked fine with the default static output mode and the Netlify adapter.This appears to be a breaking change / regression.
I had a similar issue with the netlify adapter: when using server:defer there was a problem on the netlify server with server islands (#16049 ).
The fix was a simple change in order of execution by the netlify adapter. I suspect a similar issue here.
What's the expected result?
The output "static" config should suffice to use Astro Actions with the netlify adapter.
Link to Minimal Reproducible Example
https://github.com/PanRoR/astro-server-island-netlify
Participation