397d8f3d84
* Upgrade @astrojs/markdown-support deps and update types * Add changeset * Update changeset * Switch astro-markdown-plugins example to use rehype-autolink-headings Usage of remark-autolink-headings is discouraged in favor of the rehype counterpart: https://github.com/remarkjs/remark-autolink-headings\#remark-autolink-headings * Add stricter types for unified plugins This includes a few suggestions from a code review: - use vfile.toString instead of vfile.value.toString - refactor plugins to follow unified best practices instead of returning functions that return a plugin - use any instead of any[] for plugin options types * Narrow down types to more specific hast or mdast typings |
||
|---|---|---|
| .. | ||
| blog | ||
| blog-multiple-authors | ||
| docs | ||
| framework-lit | ||
| framework-multiple | ||
| framework-preact | ||
| framework-react | ||
| framework-solid | ||
| framework-svelte | ||
| framework-vue | ||
| minimal | ||
| portfolio | ||
| snowpack | ||
| starter | ||
| with-markdown | ||
| with-markdown-plugins | ||
| with-nanostores | ||
| with-tailwindcss | ||
| README.md | ||
Astro Examples Library
The easiest way to check out one of these examples on your machine is by running this command in an empty directory:
npm init astro -- --template [EXAMPLE_NAME]
Community Examples
Visit awesome-astro for a full list of community examples. You can use npm init astro to check out any community examples:
npm init astro -- --template [GITHUB_USER]/[REPO_NAME]
Paths to examples nested inside of a repo are also supported:
npm init astro -- --template [GITHUB_USER]/[REPO_NAME]/path/to/example