🚀 Astro Next (0.21.0)

[drwpow]

🚀 Astro Next (0.21.0)

Hello! This PR showcases a huge change to Astro, namely the new Go/WASM compiler, and switch to Vite. So this will work a little differently from most PRs. This will be a long-running PR that other PRs get merged into (no pushes directly, please!).

👀 For Viewers

If you’re using this to track the status of astro@next--compiler

✨ Try it today

⚠️ We recommend starting with a new project! Trying to use on an existing Astro project will likely not work until we have full feature parity.

npm install astro@next--compiler

Examples Checklist - Complete, Linked

Status: started

• blog (jn)
• blog-multiple-authors (dp)
• docs (jn)
• framework-preact (mp)
• framework-react (mp)
• framework-svelte (mp)
• framework-vue (mp)
• framework-solid (mp)
• framework-lit (mp)
• framework-multiple (mp)
• minimal (mp)
• portfolio (jn)
• starter (mp)
• with-markdown (nm)
• with-markdown-plugins (mp)
• with-nanostores (mp)

Examples Checklist - Complete, Installed/Unlinked

Status: finished

• *shared/general: (mp) astro@next - terser issue stackblitz/webcontainer-core#335 (also: 🚀 Astro Next (0.21.0) #1406 (comment))
• blog (jn)
• blog-multiple-authors (jn)
• docs (jn
• framework-preact (nm)
• framework-react (nm)
• framework-svelte (nm)
• framework-vue (nm)
• framework-solid (mp)
• framework-lit (mp)
• framework-multiple (dp)
• minimal (jn)
• portfolio (dp)
• starter (mp)
• with-markdown (dp)
• with-markdown-plugins (nm)
• with-nanostores (dp)

🧩 Stability

Last updated: 2021-10-11

• Enable Windows tests
• Compiler needs scoping support for dynamic classes added in expressions fix: scope dynamic expressions compiler#120
• New features
  • Define vars for script & style
  • Astro components in Markdown
• Frameworks
  • Preact
  • React
  • Solid
  • Svelte
  • Vue
  • Lit Element / Custom Elements
  • slots in client components
• API
  • Astro.fetchContent() [next] Fix Astro.fetchContent #1480
  • Astro.resolve() feat(ssr): add import.meta.pathname as url in ssr vitejs/vite#5252
  • getStaticPaths()
• Markdown support
  • Markdown plugins
• Core features
  • RSS
  • Sitemap
  • Scoped CSS
  • Page-based routing
  • Builtin Astro Components (Debug, Code, etc)
    • Code [next] Fix <Code> component #1635
    • Debug [next] Simplify Debug component #1633
    • Markdown [next] Fix <Markdown> component #1631
    • Prism
  • Top-level fetch in Astro pages
  • Top-level fetch in Astro components
  • Top-level fetch in any JS-like file
• Integrations
  • PostCSS
  • Sass

🔧 For Contributors

For people helping move astro@next--compiler closer to stable release

✅ Contributing checklist

This next branch will act as a sort of main until it’s ready to merge. So in that sense, we’ll require the following workflow here:

• ✅ No commits directly to main. This should be enforced in GitHub.
• ✅ All contributions to next must be PRs targeted against this branch
• ✅ Your test suite must fully pass! (npm run test locally; ignore failing CI for now)

⏭ Moving to main

We’ll merge this PR into main when the Stability checklist above has been completed. Some items are intentionally left out, because they can be completed post-merge, with community involvement. This is including, but not limited to:

• CSS bundling
• Tailwind HMR
• client:only
• Allow using scripts in public/
  • Works as expected if not used within a page.
  • If used within a page the build fails.
• Better astro build stats output
• Fine-tuned build optimizations
• Automatic <img> and srcset inclusion
• Functional components in frontmatter
• Drop TSX/JSX support in frontmatter/compiler now that functional components not needed
• getStaticPaths() is no longer allowed to live further down the frontmatter
• Migration errors/warnings (if a user has Snowpack config, warn! if a user has old settings, warn! etc. etc.)
• with-tailwindcss (mp)
  • Build: Styles are not built, because there is no HTML scanning during the build.
  • This is being added.

[changeset-bot]

🦋 Changeset detected

Latest commit: 9f4e73f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 9 packages

Name	Type
@astrojs/prism	Minor
astro	Minor
@astrojs/markdown-remark	Minor
@astrojs/renderer-lit	Minor
@astrojs/renderer-preact	Minor
@astrojs/renderer-react	Minor
@astrojs/renderer-solid	Minor
@astrojs/renderer-svelte	Minor
@astrojs/renderer-vue	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployments, click below or on the icon next to each commit.

astro-www – ./www

🔍 Inspect: https://vercel.com/pikapkg/astro-www/9F4oZVDidkj8zFqAuwD8zvX15WjY
✅ Preview: Canceled

[Deployment for 4140001 canceled]

astro-docs – ./docs

🔍 Inspect: https://vercel.com/pikapkg/astro-docs/642V6taUCbAbvmtav5dCivZsNv9t
✅ Preview: Canceled

[Deployment for 4140001 canceled]

[brycewray]

Bug report re this PR.

I created a brand new project and installed with npm install astro@next--compiler. Set up the standard Astro directory structure as in the docs and put the "minimal" example's index.astro file in ./src/pages/; also used the regular scripts from "minimal"'s package.json. On running npm run dev, I got the following output:

> astro-site@0.21.0 dev
> astro dev

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@astrojs/renderer-svelte' imported from /Users/thewrays/astro-site/node_modules/astro/dist/runtime/vite/config.jsError [ERR_MODULE_NOT_FOUND]: Cannot find package '@astrojs/renderer-svelte' imported from /Users/thewrays/astro-site/node_modules/astro/dist/runtime/vite/config.js

At the request of @drwpow I then tried ./node_modules/.bin/astro dev but got the same result.

Repo: https://github.com/brycewray/astro-site

[natemoo-re]