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

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 [email protected]!

Patch Changes

• Updated dependencies [04ad44563]:
  • @astrojs/[email protected]

0.2.1

Patch Changes

• #4055 44694d8a9 Thanks @matthewp! - Handle binary data request bodies in the Node adapter

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.

Patch Changes

• #4023 4ca6a0933 Thanks @matthewp! - Fixes Node adapter to accept a request body

0.1.6

Patch Changes

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

0.1.5

Patch Changes

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

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

0.1.4

Patch Changes

• #3817 2f56664f Thanks @ran-dall! - Fix example on README.md

0.1.3

Patch Changes

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

0.1.2

Patch Changes

• Updated dependencies [4de53ecc]:
  • @astrojs/[email protected]

0.1.1

Patch Changes

• 815d62f1 Thanks @FredKSchott! - no changes.

0.1.0

Minor Changes

• #2979 9d7a4b59 Thanks @FredKSchott! - Welcome to the Astro v1.0.0 Beta! Read the official announcement for more details.

0.0.2

Patch Changes

• #2879 80034c6c Thanks @matthewp! - Netlify Adapter

  This change adds a Netlify adapter that uses Netlify Functions. You can use it like so:

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

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

0.0.2-next.0

Patch Changes

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