Closed ascorbic closed 1 day ago
Latest commit: 6bb89bc82711465d738a7a40196066893ade8b78
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
Snapshots have been released for the following packages:
astro@experimental--content-layer
🦋 warn ===============================IMPORTANT!===============================
🦋 warn Packages will be released under the experimental--content-layer tag
🦋 warn ----------------------------------------------------------------------
🦋 info npm info astro
🦋 info npm info @astrojs/prism
🦋 info npm info @astrojs/rss
🦋 info npm info create-astro
🦋 info npm info @astrojs/db
🦋 info npm info @astrojs/alpinejs
🦋 info npm info @astrojs/lit
🦋 info npm info @astrojs/markdoc
🦋 info npm info @astrojs/mdx
🦋 info npm info @astrojs/node
🦋 info npm info @astrojs/partytown
🦋 info npm info @astrojs/preact
🦋 info npm info @astrojs/react
🦋 info npm info @astrojs/sitemap
🦋 info npm info @astrojs/solid-js
🦋 info npm info @astrojs/svelte
🦋 info npm info @astrojs/tailwind
🦋 info npm info @astrojs/vercel
🦋 info npm info @astrojs/vue
🦋 info npm info @astrojs/web-vitals
🦋 info npm info @astrojs/internal-helpers
🦋 info npm info @astrojs/markdown-remark
🦋 info npm info @astrojs/studio
🦋 info npm info @astrojs/telemetry
🦋 info npm info @astrojs/underscore-redirects
🦋 info npm info @astrojs/upgrade
🦋 info astro is being published because our local version (0.0.0-content-layer-20240626124519) has not been published on npm
🦋 warn @astrojs/prism is not being published because version 3.1.0 is already published on npm
🦋 warn @astrojs/rss is not being published because version 4.0.7 is already published on npm
🦋 warn create-astro is not being published because version 4.8.0 is already published on npm
🦋 warn @astrojs/db is not being published because version 0.11.7 is already published on npm
🦋 warn @astrojs/alpinejs is not being published because version 0.4.0 is already published on npm
🦋 warn @astrojs/lit is not being published because version 4.3.0 is already published on npm
🦋 warn @astrojs/markdoc is not being published because version 0.11.1 is already published on npm
🦋 warn @astrojs/mdx is not being published because version 3.1.2 is already published on npm
🦋 warn @astrojs/node is not being published because version 8.3.2 is already published on npm
🦋 warn @astrojs/partytown is not being published because version 2.1.1 is already published on npm
🦋 warn @astrojs/preact is not being published because version 3.5.0 is already published on npm
🦋 warn @astrojs/react is not being published because version 3.6.0 is already published on npm
🦋 warn @astrojs/sitemap is not being published because version 3.1.6 is already published on npm
🦋 warn @astrojs/solid-js is not being published because version 4.4.0 is already published on npm
🦋 warn @astrojs/svelte is not being published because version 5.6.0 is already published on npm
🦋 warn @astrojs/tailwind is not being published because version 5.1.0 is already published on npm
🦋 warn @astrojs/vercel is not being published because version 7.7.2 is already published on npm
🦋 warn @astrojs/vue is not being published because version 4.5.0 is already published on npm
🦋 warn @astrojs/web-vitals is not being published because version 0.2.1 is already published on npm
🦋 warn @astrojs/internal-helpers is not being published because version 0.4.1 is already published on npm
🦋 warn @astrojs/markdown-remark is not being published because version 5.1.1 is already published on npm
🦋 warn @astrojs/studio is not being published because version 0.1.1 is already published on npm
🦋 warn @astrojs/telemetry is not being published because version 3.1.0 is already published on npm
🦋 warn @astrojs/underscore-redirects is not being published because version 0.3.4 is already published on npm
🦋 warn @astrojs/upgrade is not being published because version 0.3.1 is already published on npm
🦋 info Publishing "astro" at "0.0.0-content-layer-20240626124519"
🦋 success packages published successfully:
🦋 astro@0.0.0-content-layer-20240626124519
🦋 Creating git tag...
🦋 New tag: astro@0.0.0-content-layer-20240626124519
Snapshots have been released for the following packages:
astro@experimental--content-layer
🦋 warn ===============================IMPORTANT!===============================
🦋 warn Packages will be released under the experimental--content-layer tag
🦋 warn ----------------------------------------------------------------------
🦋 info npm info astro
🦋 info npm info @astrojs/prism
🦋 info npm info @astrojs/rss
🦋 info npm info create-astro
🦋 info npm info @astrojs/db
🦋 info npm info @astrojs/alpinejs
🦋 info npm info @astrojs/lit
🦋 info npm info @astrojs/markdoc
🦋 info npm info @astrojs/mdx
🦋 info npm info @astrojs/node
🦋 info npm info @astrojs/partytown
🦋 info npm info @astrojs/preact
🦋 info npm info @astrojs/react
🦋 info npm info @astrojs/sitemap
🦋 info npm info @astrojs/solid-js
🦋 info npm info @astrojs/svelte
🦋 info npm info @astrojs/tailwind
🦋 info npm info @astrojs/vercel
🦋 info npm info @astrojs/vue
🦋 info npm info @astrojs/web-vitals
🦋 info npm info @astrojs/internal-helpers
🦋 info npm info @astrojs/markdown-remark
🦋 info npm info @astrojs/studio
🦋 info npm info @astrojs/telemetry
🦋 info npm info @astrojs/underscore-redirects
🦋 info npm info @astrojs/upgrade
🦋 info astro is being published because our local version (0.0.0-content-layer-20240626134837) has not been published on npm
🦋 warn @astrojs/prism is not being published because version 3.1.0 is already published on npm
🦋 warn @astrojs/rss is not being published because version 4.0.7 is already published on npm
🦋 warn create-astro is not being published because version 4.8.0 is already published on npm
🦋 warn @astrojs/db is not being published because version 0.11.7 is already published on npm
🦋 warn @astrojs/alpinejs is not being published because version 0.4.0 is already published on npm
🦋 warn @astrojs/lit is not being published because version 4.3.0 is already published on npm
🦋 warn @astrojs/markdoc is not being published because version 0.11.1 is already published on npm
🦋 warn @astrojs/mdx is not being published because version 3.1.2 is already published on npm
🦋 warn @astrojs/node is not being published because version 8.3.2 is already published on npm
🦋 warn @astrojs/partytown is not being published because version 2.1.1 is already published on npm
🦋 warn @astrojs/preact is not being published because version 3.5.0 is already published on npm
🦋 warn @astrojs/react is not being published because version 3.6.0 is already published on npm
🦋 warn @astrojs/sitemap is not being published because version 3.1.6 is already published on npm
🦋 warn @astrojs/solid-js is not being published because version 4.4.0 is already published on npm
🦋 warn @astrojs/svelte is not being published because version 5.6.0 is already published on npm
🦋 warn @astrojs/tailwind is not being published because version 5.1.0 is already published on npm
🦋 warn @astrojs/vercel is not being published because version 7.7.2 is already published on npm
🦋 warn @astrojs/vue is not being published because version 4.5.0 is already published on npm
🦋 warn @astrojs/web-vitals is not being published because version 0.2.1 is already published on npm
🦋 warn @astrojs/internal-helpers is not being published because version 0.4.1 is already published on npm
🦋 warn @astrojs/markdown-remark is not being published because version 5.1.1 is already published on npm
🦋 warn @astrojs/studio is not being published because version 0.1.1 is already published on npm
🦋 warn @astrojs/telemetry is not being published because version 3.1.0 is already published on npm
🦋 warn @astrojs/underscore-redirects is not being published because version 0.3.4 is already published on npm
🦋 warn @astrojs/upgrade is not being published because version 0.3.1 is already published on npm
🦋 info Publishing "astro" at "0.0.0-content-layer-20240626134837"
🦋 success packages published successfully:
🦋 astro@0.0.0-content-layer-20240626134837
🦋 Creating git tag...
🦋 New tag: astro@0.0.0-content-layer-20240626134837
Snapshots have been released for the following packages:
astro@experimental--content-layer
🦋 warn ===============================IMPORTANT!===============================
🦋 warn Packages will be released under the experimental--content-layer tag
🦋 warn ----------------------------------------------------------------------
🦋 info npm info astro
🦋 info npm info @astrojs/prism
🦋 info npm info @astrojs/rss
🦋 info npm info create-astro
🦋 info npm info @astrojs/db
🦋 info npm info @astrojs/alpinejs
🦋 info npm info @astrojs/lit
🦋 info npm info @astrojs/markdoc
🦋 info npm info @astrojs/mdx
🦋 info npm info @astrojs/node
🦋 info npm info @astrojs/partytown
🦋 info npm info @astrojs/preact
🦋 info npm info @astrojs/react
🦋 info npm info @astrojs/sitemap
🦋 info npm info @astrojs/solid-js
🦋 info npm info @astrojs/svelte
🦋 info npm info @astrojs/tailwind
🦋 info npm info @astrojs/vercel
🦋 info npm info @astrojs/vue
🦋 info npm info @astrojs/web-vitals
🦋 info npm info @astrojs/internal-helpers
🦋 info npm info @astrojs/markdown-remark
🦋 info npm info @astrojs/studio
🦋 info npm info @astrojs/telemetry
🦋 info npm info @astrojs/underscore-redirects
🦋 info npm info @astrojs/upgrade
🦋 info astro is being published because our local version (0.0.0-content-layer-20240626163213) has not been published on npm
🦋 warn @astrojs/prism is not being published because version 3.1.0 is already published on npm
🦋 warn @astrojs/rss is not being published because version 4.0.7 is already published on npm
🦋 warn create-astro is not being published because version 4.8.0 is already published on npm
🦋 warn @astrojs/db is not being published because version 0.11.7 is already published on npm
🦋 warn @astrojs/alpinejs is not being published because version 0.4.0 is already published on npm
🦋 warn @astrojs/lit is not being published because version 4.3.0 is already published on npm
🦋 warn @astrojs/markdoc is not being published because version 0.11.1 is already published on npm
🦋 warn @astrojs/mdx is not being published because version 3.1.2 is already published on npm
🦋 warn @astrojs/node is not being published because version 8.3.2 is already published on npm
🦋 warn @astrojs/partytown is not being published because version 2.1.1 is already published on npm
🦋 warn @astrojs/preact is not being published because version 3.5.0 is already published on npm
🦋 warn @astrojs/react is not being published because version 3.6.0 is already published on npm
🦋 warn @astrojs/sitemap is not being published because version 3.1.6 is already published on npm
🦋 warn @astrojs/solid-js is not being published because version 4.4.0 is already published on npm
🦋 warn @astrojs/svelte is not being published because version 5.6.0 is already published on npm
🦋 warn @astrojs/tailwind is not being published because version 5.1.0 is already published on npm
🦋 warn @astrojs/vercel is not being published because version 7.7.2 is already published on npm
🦋 warn @astrojs/vue is not being published because version 4.5.0 is already published on npm
🦋 warn @astrojs/web-vitals is not being published because version 0.2.1 is already published on npm
🦋 warn @astrojs/internal-helpers is not being published because version 0.4.1 is already published on npm
🦋 warn @astrojs/markdown-remark is not being published because version 5.1.1 is already published on npm
🦋 warn @astrojs/studio is not being published because version 0.1.1 is already published on npm
🦋 warn @astrojs/telemetry is not being published because version 3.1.0 is already published on npm
🦋 warn @astrojs/underscore-redirects is not being published because version 0.3.4 is already published on npm
🦋 warn @astrojs/upgrade is not being published because version 0.3.1 is already published on npm
🦋 info Publishing "astro" at "0.0.0-content-layer-20240626163213"
🦋 success packages published successfully:
🦋 astro@0.0.0-content-layer-20240626163213
🦋 Creating git tag...
🦋 New tag: astro@0.0.0-content-layer-20240626163213
This is the work-in-progress branch implementing the Content Layer RFC.
Testing
There is an example site in the content-layer fixture, which shows the use of a custom loader and the
file()
loader. Currently the API for end user looks like this:The
blog
collection shows a custom loader. These can be defined like this:The API is currently defined like this:
Currently there is no support for loading md or mdx files using
glob()
, or for defining renderers.Querying is currently limited to
getCollection
andgetDataEntryById
, with no filter options.To test this, install the experimental version with
npm install astro@experimental--content-layer
Docs