Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
[email protected]
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', });
#4018
0cc6ede36
Thanks @okikio! - Support for 404 and 500 pages in SSR#3992
ccae43142
Thanks @matthewp! - Removes warnings for integrations/ssr#3973
5a23483ef
Thanks @matthewp! - Adds support for Astro.clientAddressThe new
Astro.clientAddress
property allows you to get the IP address of the requested user.This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.
#3570
04070c0c1
Thanks @matthewp! - Bump to Vite 3!#4016
00fab4ce1
Thanks @bholmesdev! - The use of components and JSX expressions in Markdown are no longer supported by default.For long term support, migrate to the
@astrojs/mdx
integration for MDX support (including.mdx
pages!).Not ready to migrate to MDX? Add the legacy flag to your Astro config to re-enable the previous Markdown support.
#3986
bccd88f0e
Thanks @matthewp! - Move the Markdown component to its own packageThis change moves the Markdown component into its own package where it will be maintained separately. All that needs to change from a user's perspective is the import statement:
Becomes:
Patch Changes
#3988
9841c21e8
Thanks @Princesseuh! - Fix certain characters showing incorrectly inastro check
#4000
1c1b9da62
Thanks @tony-sull! - public assets should always take priority over page routes in SSR deployments#4042
7e5ac1f45
Thanks @matthewp! - Ensure the before-hydration scripts are built#3944
e82ff13f1
Thanks @mihkeleidast! - Add export keyword to astro config file stub created by add cli command#3942
21462feb4
Thanks @AllanChain! - Use a base middleware for better base path handling in dev.#3991
4dd341c8a
Thanks @natemoo-re! - #3859 Overhaul Astro error handling, using Vite's built-in error overlay when possible#4024
1215e731b
Thanks @natemoo-re! - BREAKING Implement RFC0012 to preserve authored specificity for Astro scoped styles.If you use a mix of global styles and Astro scoped styles, please visually inspect your site after upgrading to confirm that styles are working as expected.
If you previously relied on Astro's scoped styles to increase the specificity of your selectors, please update your selectors to use an additional class. For example, updating
div
todiv.my-class
will match the previous behavior.#4046
c811be49a
Thanks @matthewp! - Adds warnings for legacy markdown behavior#4009
01ba07d8f
Thanks @matthewp! - Fixes Lit compat with Vite 3.0.1#4008
399d7e269
Thanks @bholmesdev! - Avoid parsing JSX, components, and Astro islands when using "plain" md mode. This bringsmarkdown.mode: 'md'
in-line with our docs description.#4047
453c026aa
Thanks @matthewp! - Perf: move getStaticPaths call during the build to during page generation#3974
54865612e
Thanks @Princesseuh! - Added missingmedia
attributes from the JSX definitions for themeta
element#3932
27ee8b97a
Thanks @natemoo-re! - Overhaul HMR handling for more stable live reload behavior#4044
6f88597c3
Thanks @lostra01! - Added missing "loading" attribute to IFrameHTMLAttributes#3995
b2b367c96
Thanks @bholmesdev! - Support YAML frontmatter in MDX files#3976
fbef6a7f7
Thanks @natemoo-re! - Fixdefine:vars
bugs with bothstyle
andscript
#4023
4ca6a0933
Thanks @matthewp! - Fixes Node adapter to accept a request body#4010
d503c5bf3
Thanks @matthewp! - Allow defining aliases with tsconfig#4032
beddf073b
Thanks @arimgibson! - Fix: find a hosting network differently based on Node version -- adjusted for Node v18.4+#3867
7250e4e86
Thanks @natemoo-re! - Add support for.html
components and pages#3959
ddefb172f
Thanks @FredKSchott! - Deprecate Astro.canonicalURL, in favor of Astro.url instead.#3968
95eaa207d
Thanks @bholmesdev! - Improve warning logs on astro.config change#3959
ddefb172f
Thanks @FredKSchott! - Add Astro.url helper for getting the request URL#4031
6e27a5fdc
Thanks @natemoo-re! - BREAKING Renamed Markdown utility functiongetHeaders()
togetHeadings()
.Updated dependencies [
ba11b3399
,399d7e269
,00fab4ce1
,6e27a5fdc
]:@astrojs/[email protected]
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', });
#4018
0cc6ede36
Thanks @okikio! - Support for 404 and 500 pages in SSR#3973
5a23483ef
Thanks @matthewp! - Adds support for Astro.clientAddressThe new
Astro.clientAddress
property allows you to get the IP address of the requested user.This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.
@astrojs/[email protected]
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', });
#3973
5a23483ef
Thanks @matthewp! - Adds support for Astro.clientAddressThe new
Astro.clientAddress
property allows you to get the IP address of the requested user.This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.
@astrojs/[email protected]
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', });
#3570
04070c0c1
Thanks @matthewp! - Bump to Vite 3!#4013
ef9345767
Thanks @tony-sull! - - Fixes two bugs that were blocking SSR support when deployed to a hosting servicesharp
service now automatically rotates images based on EXIF dataPatch 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@astrojs/[email protected]
Minor Changes
#3977
19433eb4a
Thanks @bholmesdev! - Add remarkPlugins and rehypePlugins to config, with the same default plugins as our standard Markdown parser#4002
3b8a74452
Thanks @bholmesdev! - Support Prism and Shiki syntax highlighting based on project config#3995
b2b367c96
Thanks @bholmesdev! - Support YAML frontmatter in MDX filesPatch Changes
#4050
9ab66c4ba
Thanks @FredKSchott! - Add support for injected "page-ssr" scripts#3981
61fec6304
Thanks @bholmesdev! - Include page url in MDX glob result@astrojs/[email protected]
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', });
#4018
0cc6ede36
Thanks @okikio! - Support for 404 and 500 pages in SSR#3973
5a23483ef
Thanks @matthewp! - Adds support for Astro.clientAddressThe new
Astro.clientAddress
property allows you to get the IP address of the requested user.This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.
@astrojs/[email protected]
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', });
#3973
5a23483ef
Thanks @matthewp! - Adds support for Astro.clientAddressThe new
Astro.clientAddress
property allows you to get the IP address of the requested user.This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.
Patch Changes
4ca6a0933
Thanks @matthewp! - Fixes Node adapter to accept a request body@astrojs/[email protected]
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', });
Patch Changes
#3978
b37d7078a
Thanks @Chrissdroid! - Update README to reflect@astrojs/[email protected]
changes#4004
ef9c4152b
Thanks @sarah11918! - [READMEs] removed "experimental" from astro add instructions@astrojs/[email protected]
Minor Changes
04070c0c1
Thanks @matthewp! - Bump to Vite 3!Patch Changes
40a45e3ef
Thanks @Princesseuh! - Fix optional props not being recognized properly in the editor@astrojs/[email protected]
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', });
#4018
0cc6ede36
Thanks @okikio! - Support for 404 and 500 pages in SSR#3973
5a23483ef
Thanks @matthewp! - Adds support for Astro.clientAddressThe new
Astro.clientAddress
property allows you to get the IP address of the requested user.This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.
#4020
1666fdb4c
Thanks @JuanM04! - Removed requirement forENABLE_VC_BUILD=1
, since Build Output v3 is now stable. Learn more.@astrojs/[email protected]
Minor Changes
04070c0c1
Thanks @matthewp! - Bump to Vite 3!@astrojs/[email protected]
Minor Changes
#4016
00fab4ce1
Thanks @bholmesdev! - The use of components and JSX expressions in Markdown are no longer supported by default.For long term support, migrate to the
@astrojs/mdx
integration for MDX support (including.mdx
pages!).Not ready to migrate to MDX? Add the legacy flag to your Astro config to re-enable the previous Markdown support.
#3986
bccd88f0e
Thanks @matthewp! - Move the Markdown component to its own packageThis change moves the Markdown component into its own package where it will be maintained separately. All that needs to change from a user's perspective is the import statement:
Becomes:
@astrojs/[email protected]
Minor Changes
ba11b3399
Thanks @RafidMuhymin! - fixed generated slugs in markdown that ends with a dash#4016
00fab4ce1
Thanks @bholmesdev! - The use of components and JSX expressions in Markdown are no longer supported by default.For long term support, migrate to the
@astrojs/mdx
integration for MDX support (including.mdx
pages!).Not ready to migrate to MDX? Add the legacy flag to your Astro config to re-enable the previous Markdown support.
#4031
6e27a5fdc
Thanks @natemoo-re! - BREAKING Renamed Markdown utility functiongetHeaders()
togetHeadings()
.Patch Changes
399d7e269
Thanks @bholmesdev! - Avoid parsing JSX, components, and Astro islands when using "plain" md mode. This bringsmarkdown.mode: 'md'
in-line with our docs description.[email protected]
Patch Changes
e6e216061
Thanks @tony-sull! - Fixes support for using templates from any GitHub repository@astrojs/[email protected]
Patch Changes
01ba07d8f
Thanks @matthewp! - Fixes Lit compat with Vite 3.0.1@astrojs/[email protected]
Patch Changes
ef9c4152b
Thanks @sarah11918! - [READMEs] removed "experimental" from astro add instructions@astrojs/[email protected]
Patch Changes
ef9c4152b
Thanks @sarah11918! - [READMEs] removed "experimental" from astro add instructions@astrojs/[email protected]
Patch Changes
ef9c4152b
Thanks @sarah11918! - [READMEs] removed "experimental" from astro add instructions