You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adapters are now about to support the `astro preview` command via a new integration option. The Node.js adapter `@astrojs/node` is the first of the built-in adapters to gain support for this. What this means is that if you are using `@astrojs/node` you can new preview your SSR app by running:
9
+
10
+
```shell
11
+
npm run preview
12
+
```
13
+
14
+
## Adapter API
15
+
16
+
We will be updating the other first party Astro adapters to support preview over time. Adapters can opt-in to this feature by providing the `previewEntrypoint` via the `setAdapter` function in `astro:config:done` hook. The Node.js adapter's code looks like this:
The `previewEntrypoint` is a module in the adapter's package that is a Node.js script. This script is run when `astro preview` is run and is charged with starting up the built server. See the Node.js implementation in `@astrojs/node` to see how that is implemented.
New in `@astrojs/node` is support for __standalone mode__. With standalone mode you can start your production server without needing to write any server JavaScript yourself. The server starts simply by running the script like so:
8
+
9
+
```shell
10
+
node ./dist/server/entry.mjs
11
+
```
12
+
13
+
To enable standalone mode, set the new `mode` to `'standalone'` option in your Astro config:
14
+
15
+
```js
16
+
import { defineConfig } from'astro/config';
17
+
importnodejsfrom'@astrojs/node';
18
+
19
+
exportdefaultdefineConfig({
20
+
output:'server',
21
+
adapter:nodejs({
22
+
mode:'standalone'
23
+
})
24
+
});
25
+
```
26
+
27
+
See the @astrojs/node documentation to learn all of the options available in standalone mode.
28
+
29
+
## Breaking change
30
+
31
+
This is a semver major change because the new `mode` option is required. Existing @astrojs/node users who are using their own HTTP server framework such as Express can upgrade by setting the `mode` option to `'middleware'` in order to build to a middleware mode, which is the same behavior and API as before.
The ability to customize SSR build configuration more granularly is now available in Astro. You can now customize the output folder for `server` (the server code for SSR), `client` (your client-side JavaScript and assets), and `serverEntry` (the name of the entrypoint server module). Here are the defaults:
14
+
15
+
```js
16
+
import { defineConfig } from'astro/config';
17
+
18
+
exportdefaultdefineConfig({
19
+
output:'server',
20
+
build: {
21
+
server:'./dist/server/',
22
+
client:'./dist/client/',
23
+
serverEntry:'entry.mjs',
24
+
}
25
+
});
26
+
```
27
+
28
+
These new configuration options are only supported in SSR mode and are ignored when building to SSG (a static site).
29
+
30
+
## Integration hook change
31
+
32
+
The integration hook `astro:build:start` includes a param `buildConfig` which includes all of these same options. You can continue to use this param in Astro 1.x, but it is deprecated in favor of the new `build.config` options. All of the built-in adapters have been updated to the new format. If you have an integration that depends on this param we suggest upgrading to do this instead:
0 commit comments