🚀 Astro Next (0.21.0)

.changeset/dull-bikes-doubt.md

@@ -0,0 +1,5 @@
+---
+'@astrojs/prism': minor
+---
+
+Adds typings for the main entrypoint

.changeset/pink-trainers-learn.md

@@ -0,0 +1,11 @@
+---
+'astro': minor
+---
+
+Astro 0.21 Beta release! This introduces the new version of Astro that includes:
+
+- A new, faster, Go-based compiler
+- A runtime backed by Vite, with faster dev experience
+- New features
+
+See more at https://astro.build/blog/astro-021-preview/

.changeset/pre.json

@@ -0,0 +1,40 @@
+{
+  "mode": "pre",
+  "tag": "next",
+  "initialVersions": {
+    "docs": "0.0.7",
+    "@example/blog": "0.0.1",
+    "@example/blog-multiple-authors": "0.0.1",
+    "@example/docs": "0.0.1",
+    "@example/framework-lit": "0.0.1",
+    "@example/framework-multiple": "0.0.1",
+    "@example/framework-preact": "0.0.1",
+    "@example/framework-react": "0.0.1",
+    "@example/framework-solid": "0.0.1",
+    "@example/framework-svelte": "0.0.1",
+    "@example/framework-vue": "0.0.1",
+    "@example/minimal": "0.0.1",
+    "@example/portfolio": "0.0.1",
+    "@example/starter": "0.0.1",
+    "@example/with-markdown": "0.0.1",
+    "@example/with-markdown-plugins": "0.0.2",
+    "@example/with-nanostores": "0.0.1",
+    "@example/with-tailwindcss": "0.0.1",
+    "astro": "0.20.12",
+    "@astrojs/parser": "0.20.2",
+    "@astrojs/prism": "0.2.2",
+    "@astrojs/astro-test-builtins-dep": "0.0.1",
+    "@astrojs/test-custom-element-renderer": "0.0.1",
+    "create-astro": "0.6.6",
+    "@astrojs/markdown-remark": "0.3.1",
+    "@astrojs/renderer-lit": "0.1.2",
+    "@astrojs/renderer-preact": "0.2.2",
+    "@astrojs/renderer-react": "0.2.2",
+    "@astrojs/renderer-solid": "0.1.1",
+    "@astrojs/renderer-svelte": "0.1.2",
+    "@astrojs/renderer-vue": "0.1.9",
+    "astro-scripts": "0.0.1",
+    "www": "1.1.0"
+  },
+  "changesets": []
+}

.changeset/silly-apples-build.md

@@ -0,0 +1,5 @@
+---
+'@astrojs/markdown-remark': minor
+---
+
+Adds prism support within the Markdown plugin.

.changeset/tiny-bulldogs-lie.md

@@ -0,0 +1,10 @@
+---
+'@astrojs/renderer-lit': minor
+'@astrojs/renderer-preact': minor
+'@astrojs/renderer-react': minor
+'@astrojs/renderer-solid': minor
+'@astrojs/renderer-svelte': minor
+'@astrojs/renderer-vue': minor
+---
+
+Updates the renderers to confirm to the new renderer API.

.eslintignore

@@ -3,3 +3,4 @@
 !packages/astro/**/*.js
 !packages/astro/**/*.ts
 packages/astro/test/**/*.js
+packages/astro/vendor/vite/**/*

.eslintrc.cjs

@@ -8,13 +8,13 @@ module.exports = {
     '@typescript-eslint/explicit-module-boundary-types': 'off',
     '@typescript-eslint/no-empty-function': 'off',
     '@typescript-eslint/no-explicit-any': 'off',
+    '@typescript-eslint/no-non-null-assertion': 'off',
     '@typescript-eslint/no-unused-vars': 'off',
     '@typescript-eslint/no-use-before-define': 'off',
     '@typescript-eslint/no-var-requires': 'off',
     'no-console': 'warn',
     'no-shadow': 'error',
     'prefer-const': 'off',
-    'prefer-rest-params': 'off',
-    'require-jsdoc': 'off',
+    // 'require-jsdoc': 'error', // re-enable this to enforce JSDoc for all functions
   },
 };

.github/workflows/ci.yml

@@ -18,11 +18,13 @@ jobs:
       matrix:
         os: [ubuntu-latest]
         node_version: [12, 14, 16]
-        include:
-          - os: windows-latest
-            node_version: 14
+        # TODO: uncomment this (Vite has trouble resolving imports on Windows)
+        # include:
+        #   - os: windows-latest
+        #     node_version: 14
       fail-fast: false
-
+    env:
+      LANG: en-us
     name: 'Test: node-${{ matrix.node_version }}, ${{ matrix.os }}'
     steps:
       - name: Checkout
@@ -72,33 +74,34 @@ jobs:
       - name: Lint
         run: yarn lint
 
-  smoke:
-    runs-on: ubuntu-latest
-    name: 'Smoke: node-14, ubuntu-latest'
-    steps:
-      - uses: actions/checkout@v2
-        with:
-          fetch-depth: 0
-
-      - name: Set node version to 14
-        uses: actions/setup-node@v2
-        with:
-          node-version: 14
-          cache: 'yarn'
-
-      - name: Debug
-        run: yarn versions
-
-      - name: Install dependencies
-        run: yarn install --frozen-lockfile --ignore-engines
-
-      - name: Build
-        run: yarn build:all
-
-      - name: "Smoke Test: Build 'docs'"
-        run: yarn build
-        working-directory: ./docs
-
-      - name: "Smoke Test: Build 'www'"
-        run: yarn build
-        working-directory: ./www
+  # NOTE: temporarily disabled until `next` branch can build docs again
+  # smoke:
+  #   runs-on: ubuntu-latest
+  #   name: 'Smoke: node-14, ubuntu-latest'
+  #   steps:
+  #     - uses: actions/checkout@v2
+  #       with:
+  #         fetch-depth: 0
+
+  #     - name: Set node version to 14
+  #       uses: actions/setup-node@v2
+  #       with:
+  #         node-version: 14
+  #         cache: 'yarn'
+
+  #     - name: Debug
+  #       run: yarn versions
+
+  #     - name: Install dependencies
+  #       run: yarn install --frozen-lockfile --ignore-engines
+
+  #     - name: Build
+  #       run: yarn build:all
+
+  #     - name: "Smoke Test: Build 'docs'"
+  #       run: yarn build
+  #       working-directory: ./docs
+
+  #     - name: "Smoke Test: Build 'www'"
+  #       run: yarn build
+  #       working-directory: ./www

.gitignore

@@ -12,3 +12,5 @@ package-lock.json
 
 # do not commit .env files or any files that end with `.env`
 *.env
+
+!packages/astro/vendor/vite/dist

CONTRIBUTING.md

@@ -5,15 +5,17 @@ We welcome contributions of any size and skill level. As an open source project,
 > **Tip for new contributors:**
 > Take a look at [https://github.com/firstcontributions/first-contributions](https://github.com/firstcontributions/first-contributions) for helpful information on contributing
 
-## Prerequisite
+## Quick Guide
+
+### Prerequisite
 
 ```shell
 node: "^12.20.0 || ^14.13.1 || >=16.0.0"
 yarn: "^1.22.10"
 # otherwise, your build will fail
 ```
 
-## Setting up your local repo
+### Setting up your local repo
 
 Astro uses yarn workspaces, so you should **always run `yarn install` from the top-level project directory.** running `yarn install` in the top-level project root will install dependencies for `astro`, `www`, `docs`, and every package in the repo.
 
@@ -23,7 +25,7 @@ yarn install
 yarn build:all
 ```
 
-## Development
+### Development
 
 ```shell
 # starts a file-watching, live-reloading dev script for active development
@@ -32,17 +34,26 @@ yarn dev
 yarn build
 ```
 
-## Running tests
+#### Debugging Vite
+
+You can debug vite by prefixing any command with `DEBUG` like so:
+
+```
+DEBUG=vite:* astro dev        # debug everything in Vite
+DEBUG=vite:[name] astro dev   # debug specific process, e.g. "vite:deps" or "vite:transform"
+```
+
+### Running tests
 
 ```shell
 # run this in the top-level project root to run all tests
 yarn test
 # run only a few tests, great for working on a single feature
-# (example - `yarn test rss` runs `astro-rss.test.js` tests)
-yarn test $STRING_MATCH
+# (example - `yarn test -g "RSS"` runs `astro-rss.test.js`)
+yarn test -g "$STRING_MATCH"
 ```
 
-## Other useful commands
+### Other useful commands
 
 ```shell
 # auto-format the entire project
@@ -56,15 +67,15 @@ yarn format
 yarn lint
 ```
 
-## Making a Pull Request
+### Making a Pull Request
 
 When making a pull request, be sure to add a changeset when something has changed with Astro. Non-packages (`examples/*`, `docs/*`, and `www/*`) do not need changesets.
 
 ```shell
 yarn changeset
 ```
 
-## Running benchmarks
+### Running benchmarks
 
 We have benchmarks to keep performance under control. You can run these by running (from the project root):
 
@@ -83,15 +94,39 @@ node test/benchmark/dev.bench.js --save
 
 Which will update the build and dev benchmarks.
 
-# Releasing Astro
+## Code Structure
+
+Server-side rendering (SSR) can be complicated. The Astro package (`packages/astro`) is structured in a way to help think about the different systems.
+
+- `components/`: Built-in components to use in your project (e.g. `import Code from 'astro/components/Code.astro'`)
+- `src/`: Astro source
+  - `@types/`: TypeScript types. These are centralized to cut down on circular dependencies
+  - `cli/`: Code that powers the `astro` CLI command
+  - `core/`: Code that executes **in the top-level scope** (in Node). Within, you’ll find code that powers the `astro build` and `astro dev` commands, as well as top-level SSR code.
+  - `runtime/`: Code that executes **in different scopes** (i.e. not in a pure Node context). You’ll have to think about code differently here.
+    - `client/`: Code that executes **in the browser.** Astro’s partial hydration code lives here, and only browser-compatible code can be used.
+    - `server/`: Code that executes **inside Vite’s SSR.** Though this is a Node environment inside, this will be executed independently from `core/` and may have to be structured differently.
+  - `vite-plugin-*/`: Any Vite plugins that Astro needs to run. For the most part, these also execute within Vite similar to `src/runtime/server/`, but it’s also helpful to think about them as independent modules. _Note: at the moment these are internal while they’re in development_
+
+### Thinking about SSR
+
+There are 3 contexts in which code executes:
+
+- **Node.js**: this code lives in `src/core/`.
+- **Inside Vite**: this code lives in `src/runtime/server/`.
+- **In the browser**: this code lives in `src/runtime/client/`.
+
+Understanding in which environment code runs, and at which stage in the process, can help clarify thinking about what Astro is doing. It also helps with debugging, for instance, if you’re working within `src/core/`, you know that your code isn’t executing within Vite, so you don’t have to debug Vite’s setup. But you will have to debug vite inside `runtime/server/`.
+
+## Releasing Astro
 
 _Note: Only priviledged contributors (L3+) can release new versions of Astro._
 
 The repo is set up with automatic releases, using the changeset GitHub action & bot.
 
 To release a new version of Astro, find the `Version Packages` PR, read it over, and merge it.
 
-## Releasing PR preview snapshots
+### Releasing PR preview snapshots
 
 Our release tool `changeset` has a feature for releasing "snapshot" releases from a PR or custom branch. These are npm package publishes that live temporarily, so that you can give users a way to test a PR before merging. This can be a great way to get early user feedback while still in the PR review process.
 
@@ -112,7 +147,7 @@ git reset --hard
 
 Full documentation: https://github.com/atlassian/changesets/blob/main/docs/snapshot-releases.md
 
-## Releasing `astro@next` (aka "prerelease mode")
+### Releasing `astro@next` (aka "prerelease mode")
 
 Sometimes, the repo will enter into "prerelease mode". In prerelease mode, our normal release process will publish npm versions under the `next` dist-tag, instead of the default `latest` tag. We do this from time-to-time to test large features before sharing them with the larger Astro audience.
 
@@ -154,7 +189,7 @@ When in prerelease mode, the automatic PR release process will no longer release
 1. Go to https://github.com/snowpackjs/astro/releases/new and create a new release. Copy the new changelog entry from https://github.com/snowpackjs/astro/blob/latest/packages/astro/CHANGELOG.md.
 1. Post in Discord #announcements channel, if needed!
 
-# Translations
+## Translations
 
 Help us translate [docs.astro.build](https://docs.astro.build/) into as many languages as possible! This can be a great way to get involved with open source development without having to code.
 

docs/package.json

@@ -21,7 +21,7 @@
     "broken-link-checker": "^0.7.8",
     "npm-run-all": "^4.1.5",
     "pa11y-ci": "^2.4.2",
-    "prettier": "^2.3.2",
+    "prettier": "^2.4.1",
     "start-server-and-test": "^1.12.6"
   },
   "dependencies": {

docs/src/config.ts

@@ -24,6 +24,7 @@ export const SIDEBAR = {
     { text: 'RSS', link: 'guides/rss' },
     { text: 'Supported Imports', link: 'guides/imports' },
     { text: 'Aliases', link: 'guides/aliases' },
+    { text: 'Environment Variables', link: 'guides/environment-variables' },
     { text: 'Deploy to the web', link: 'guides/deploy' },
     { text: 'Publish to npm', link: 'guides/publish-to-npm' },
 

docs/src/pages/guides/data-fetching.md

@@ -32,11 +32,10 @@ console.log(data);
 
 ## Using `fetch()` outside of Astro Components
 
-If you want to use `fetch()` in a non-astro component, use the [`node-fetch`](https://github.com/node-fetch/node-fetch) library:
+If you want to use `fetch()` in a non-astro component, it is also globally available:
 
 ```tsx
 // Movies.tsx
-import fetch from 'node-fetch';
 import type { FunctionalComponent } from 'preact';
 import { h } from 'preact';
 
@@ -55,11 +54,3 @@ const Movies: FunctionalComponent = () => {
 
 export default Movies;
 ```
-
-If you load a component using `node-fetch` [interactively](/core-concepts/component-hydration), with `client:load`, `client:visible`, etc., you'll need to either not use `node-fetch` or switch to an [isomorphic](https://en.wikipedia.org/wiki/Isomorphic_JavaScript) library that will run both at build time and on the client, as the [`node-fetch` README.md](https://github.com/node-fetch/node-fetch#motivation) recommends:
-
-> Instead of implementing XMLHttpRequest in Node.js to run browser-specific [Fetch polyfill](https://github.com/github/fetch), why not go from native http to fetch API directly? Hence, node-fetch, minimal code for a window.fetch compatible API on Node.js runtime.
->
-> See Jason Miller's [isomorphic-unfetch](https://www.npmjs.com/package/isomorphic-unfetch) or Leonardo Quixada's [cross-fetch](https://github.com/lquixada/cross-fetch) for isomorphic usage (exports node-fetch for server-side, whatwg-fetch for client-side).
-
-> Quoted from https://github.com/node-fetch/node-fetch#motivation