- #7263
dff0d0dda
Thanks @andremralves! - Fix sitemap does not filter pages
- #7028
6ca3b5a9e
Thanks @alexanderniebuhr! - exported enum type to support typescript > 5.0
- #7029
1b90a7a5d
Thanks @TheOtterlord! - Fix generation for static dynamic routes
- #6534
ad907196c
Thanks @atilafassina! - Adds support to SSR routes to sitemap generation.
- #6658
1ec1df126
Thanks @andremralves! - Fix sitemap generation with a base path
- #6494
a13e9d7e3
Thanks @Yan-Thomas! - Consistency improvements to several package descriptions
- #6213
afbbc4d5b
Thanks @Princesseuh! - Updated compilation settings to disable downlevelling for Node 14
- #6262
4fcefa34f
Thanks @vic1707! - updateChangeFreq
to support typescript configurations with string literal or predefined value.
-
04ad44563
- > Astro v1.0 is out! Read the official announcement post.No breaking changes. This package is now officially stable and compatible with
astro@1.0.0
!
-
#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', });
- #3978
b37d7078a
Thanks @Chrissdroid! - Update README to reflect@astrojs/sitemap@0.2.0
changes
- #4004
ef9c4152b
Thanks @sarah11918! - [READMEs] removed "experimental" from astro add instructions
- #3854
b012ee55
Thanks @bholmesdev! - [astro add] Support adapters and third party packages
- #3723
52f75369
Thanks @alextim! - fix: ifserialize
function returnsundefined
for the passed entry, such entry will be excluded from sitemap
- #3689
3f8ee70e
Thanks @bholmesdev! - Add warning log for sitemap + SSR adapter, with suggestion to use customPages configuration option
-
#3579
1031c06f
Thanks @alextim! - # Key features- Split up your large sitemap into multiple sitemaps by custom limit.
- Ability to add sitemap specific attributes such as
lastmod
etc. - Final output customization via JS function.
- Localization support.
- Reliability: all config options are validated.
The integration always generates at least two files instead of one:
sitemap-index.xml
- index file;sitemap-{i}.xml
- actual sitemap.
- #3553
c601ce59
Thanks @caioferrarezi! - Prevent sitemap URLs with trimmed paths
e425f896
Thanks @FredKSchott! - Update config options to respect RFC0019
e425f896
Thanks @FredKSchott! - Add new sitemap configuration options:filter
: filter pages to include in your sitemapcanonicalURL
: override your astro.configsite
with a custom base URL
- #2885
6b004363
Thanks @bholmesdev! - Add README across Astro built-in integrations
- #2847
3b621f7a
Thanks @tony-sull! - Adds keywords to the official integrations to support discoverability on Astro's Integrations site
- #2847
3b621f7a
Thanks @tony-sull! - Adds keywords to the official integrations to support discoverability on Astro's Integrations site