Minor Changes
-
#4015
6fd161d76
Thanks @matthewp! - Newoutput
configuration optionThis change introduces a new "output target" configuration option (
output
). Setting the output target lets you decide the format of your final build, either:"static"
(default): A static site. Your final build will be a collection of static assets (HTML, CSS, JS) that you can deploy to any static site host."server"
: A dynamic server application. Your final build will be an application that will run in a hosted server environment, generating HTML dynamically for different requests.
If
output
is omitted from your config, the default value"static"
will be used.When using the
"server"
output target, you must also include a runtime adapter via theadapter
configuration. An adapter will adapt your final build to run on the deployed platform of your choice (Netlify, Vercel, Node.js, Deno, etc).To migrate: No action is required for most users. If you currently define an
adapter
, you will need to also addoutput: 'server'
to your config file to make it explicit that you are building a server. Here is an example of what that change would look like for someone deploying to Netlify:import { defineConfig } from 'astro/config'; import netlify from '@astrojs/netlify/functions'; export default defineConfig({ adapter: netlify(), + output: 'server', });
-
#4013
ef9345767
Thanks @tony-sull! - - Fixes two bugs that were blocking SSR support when deployed to a hosting service- The built-in
sharp
service now automatically rotates images based on EXIF data
- The built-in
Patch Changes
-
#3961
d73c04a9e
Thanks @tony-sull! - Updates the component to pass thealt
attribute down to the element -
#4021
9aecf7c7c
Thanks @delucis! - Handle EXIF orientation flag -
#4048
e60d6d9c1
Thanks @tony-sull! - Removes Node'sfileURLToPath
dependency in the production SSR endpoint -
#4004
ef9c4152b
Thanks @sarah11918! - [READMEs] removed "experimental" from astro add instructions -
#3980
eaf187f2c
Thanks @tony-sull! - Fixing TypeScript definition exports for image components