Astro Integration Kit can be used in 2 ways: as extended hooks or as standalone utilities.
Which flavor should you use?
Extended hooks provide a way better DX and we recommend picking this one by default. However, if you have
an existing integration that you want to migrate to astro-integration-kit, using standalone utilities
will allow you to migrate progressively. Any standalone utility is also available as an extended hook
argument.
Extended hooks
Plugins
Astro Integration Kit is built in a modular way. By default, it brings a solid foundation
that makes it easily extendable by plugins. By default, no plugin is enabled but the package ships
with some corePlugins (documented on this website), that you can easily enable, either all at once
or one by one as needed.
This allows other developers to easily add their own plugins.
Using plugins (soon)Learn how to use plugins to fully take advantage of Astro Integration Kit.
Defining an integration
To define your integration, use the defineIntegration utility:
Learn more about defineIntegrationA powerful wrapper around the standard Astro Integrations API. It allows to provide extra hooks, functionality and best-practices when creating Astro Integrations.
Standalone utilities
Use utilities exported from astro-integration-kit/utilities: