CHANGELOG.md

@astrojs/node

1.0.1

Patch Changes

• #4558 742966456 Thanks @tony-sull! - Adding the withastro keyword to include the adapters on the Integrations Catalog

• #4562 294122b4e Thanks @zicklag! - Make Deno SSR Backend Render Custom 404 Pages

1.0.0

Major Changes

• 04ad44563 - > Astro v1.0 is out! Read the official announcement post.

  No breaking changes. This package is now officially stable and compatible with astro@1.0.0!

0.2.0

Minor Changes

• #4015 6fd161d76 Thanks @matthewp! - New output configuration option

  This change introduces a new "output target" configuration option (output). Setting the output target lets you decide the format of your final build, either:

  • "static" (default): A static site. Your final build will be a collection of static assets (HTML, CSS, JS) that you can deploy to any static site host.
  • "server": A dynamic server application. Your final build will be an application that will run in a hosted server environment, generating HTML dynamically for different requests.

  If output is omitted from your config, the default value "static" will be used.

  When using the "server" output target, you must also include a runtime adapter via the adapter configuration. An adapter will adapt your final build to run on the deployed platform of your choice (Netlify, Vercel, Node.js, Deno, etc).

  To migrate: No action is required for most users. If you currently define an adapter, you will need to also add output: 'server' to your config file to make it explicit that you are building a server. Here is an example of what that change would look like for someone deploying to Netlify:

  import { defineConfig } from 'astro/config';
  import netlify from '@astrojs/netlify/functions';
  
  export default defineConfig({
    adapter: netlify(),
  + output: 'server',
  });

• #3973 5a23483ef Thanks @matthewp! - Adds support for Astro.clientAddress

  The new Astro.clientAddress property allows you to get the IP address of the requested user.

  This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.

0.1.10

Patch Changes

• #3885 bf5d1cc1e Thanks @delucis! - Integration README fixes

0.1.9

Patch Changes

• #3865 1f9e4857 Thanks @delucis! - Small README fixes

• #3854 b012ee55 Thanks @bholmesdev! - [astro add] Support adapters and third party packages

0.1.8

Patch Changes

• #3677 8045c8ad Thanks @Jutanium! - Update READMEs

0.1.7

Patch Changes

• #3734 4acd245d Thanks @bholmesdev! - Fix: append shim to top of built file to avoid "can't read process of undefined" issues

0.1.6

Patch Changes

• #3673 ba5ad785 Thanks @hippotastic! - Fix react dependencies to improve test reliability

0.1.5

Patch Changes

• #3532 c22a07db Thanks @matthewp! - Fix for using Astro.glob when using the Deno Deploy adapter

0.1.4

Patch Changes

• #3503 207f58d1 Thanks @williamtetlow! - Alias from 'astro' imports to '@astro/types' Update Deno and Netlify integrations to handle vite.resolves.alias as an array

0.1.3

Patch Changes

• #3483 b795a085 Thanks @mvolfik! - Deno integration now loads environment variables in server runtime

0.1.2

Patch Changes

• #3160 ae9ac5cb Thanks @matthewp! - Allows using React.lazy, Suspense in SSR and with hydration

0.1.1

Patch Changes

• #3121 e5383cd3 Thanks @matthewp! - Handles file serving in the main export

0.1.0

Minor Changes

• e425f896 Thanks @FredKSchott! - Update config options to resepect RFC0019

Patch Changes

• e425f896 Thanks @FredKSchott! - Add a Deno adapter for SSR

0.0.2-next.0

Patch Changes

• #2873 e4025d1f Thanks @matthewp! - Improves the build by building to a single file for rendering