{{ message }}
Repository navigation
Conversation
Contributor
e18e dependency analysisNo dependency warnings found. |
ematipico
force-pushed
the
feat/joined-apis
branch
from
October 23, 2026 13:12
0855468 to
044148d
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Changes
experimental.liveContentEntrypoints. With it, live collections can be declared insrc/content.config.tsnext to build-time collections, asdefineCollection({ type: 'live', entrypoint: './src/live/products.ts' }). The entrypoint default-exportsdefineLiveCollection({ loader, schema }), one live collection per module, sosrc/live.config.tsisn't needed. It keeps working alongside entrypoints.astro:contentruntime gets a map of lazyimport()s of the entrypoints, so the server bundle contains only the live modules and their imports, not build-time loaders. Entrypoints load on first use, which lets them importastro:contentwithout thelive.config.tsredirect.LiveContentConfigErrorwhen the flag is off or an entrypoint doesn't exist. Types are generated from each entrypoint's default export intoLiveContentConfig, merged withlive.config.ts, and live collections are left out ofDataEntryMap.astro:contentmodule and the types are unchanged.Testing
live-loaders.test.tsruns its existing dev and SSR assertions against a newlive-loaders-entrypointsfixture, unchanged. It also checks that the server chunks include the entrypoint but not the glob loader or the content config, and that the build fails without the flag.units/content-layer/live-entrypoints.test.ts) coverdefineCollection()validation,defineLiveCollection()in entrypoints, and lazy loading ingetLiveCollection()/getLiveEntry(), including an entrypoint that doesn't export a live collection.types/define-collection-entrypoint.ts) cover thedefineCollection()overload.Docs
@docsentry intypes/public/config.ts, which generates the configuration reference. Content collection guides can be updated when the flag is stable./cc @withastro/maintainers-docs for feedback!