Astro Node.js Fastify

This adapter uses the Fastify web framework which allows Astro to deploy SSR sites to Node.js targets. It also compresses asset and SSR responses by default.

Table of contents

• Astro Node.js Fastify
  • Table of contents
  • Quickstart
  • Usage
  • Configuration Example
  • Configuration
  • Troubleshooting
    • Common Issues and Solutions
      • Compression Not Working
      • 404 Errors for Assets in Dot Files/Directories
      • Static Assets Not Caching Properly
      • Server Running Out of Memory
      • Issues Behind a Reverse Proxy
    • Getting Help

Quickstart

1. Install via the package manager of your choice
   • Example via NPM: npm i --save-prod astro-node-fastify
   • Or via the Astro CLI: astro add astro-node-fastify
2. Build your site
3. Either start a preview or the standalone entry.

Usage

Add this package as a runtime dependency using your preferred package manager.

Once installed, you can customize various aspects of your Astro application through configuration options. You can specify which assets should be pre-compressed to improve load times, define appropriate cache headers for files in your Astro "public" directory, and set default response headers that will apply to all server-side rendered responses.

For instance, you might configure specific cache control settings for static assets or enable particular compression algorithms like gzip or brotli.

Configuration Example

1// astro.config.mjs
2import {defineConfig} from 'astro/config';
3import nodeFastify from 'astro-node-fastify';
4
5export default defineConfig({
6    output: 'server',
7    adapter: nodeFastify({
8        // Controls whether static assets are pre-compressed at build time (true)
9        // or compressed dynamically at runtime (false).
10        // Pre-compressing improves performance by avoiding on-the-fly compression.
11        preCompressed: true,
12
13        // Specifies which compression algorithms the server should support.
14        // Browsers will choose the best available algorithm they support
15        // based on the Accept-Encoding header.
16        supportedEncodings: ['br', 'gzip'],
17
18        // Configure cache headers for static assets to optimize performance
19        // and reduce server load by leveraging browser and CDN caching.
20        cache: {
21            // Set maximum time (in seconds) that browsers should cache assets
22            // 604,800 seconds = 7 days
23            maxAge: 604800,
24
25            // Allow CDNs to serve stale content while revalidating in background
26            // 86,400 seconds = 24 hours
27            staleWhileRevalidate: 86400,
28
29            // Allow serving stale content if origin server errors occur
30            // 86,400 seconds = 24 hours
31            staleIfError: 86400
32        },
33
34        // Set HTTP headers that will be automatically included in responses
35        defaultHeaders: {
36            // Headers for dynamically generated server-side rendered pages
37            ssr: {
38                // Prevents MIME-type sniffing security issues
39                'X-Content-Type-Options': 'nosniff',
40
41                // Prevents your site from being embedded in iframes on other domains
42                // protecting against clickjacking attacks
43                'X-Frame-Options': 'SAMEORIGIN'
44            },
45
46            // Headers for static assets served from the public directory
47            asset: {
48                // Prevents MIME-type sniffing security issues
49                'X-Content-Type-Options': 'nosniff'
50            }
51        },
52
53        // Configure the underlying Fastify server behavior
54        server: {
55            // Enables HTTP request logging for monitoring and debugging
56            accessLogging: true,
57
58            // Specifies which IP addresses should be trusted when behind proxies
59            // Important for preserving correct client IP addresses in logs and for
60            // security features that depend on accurate client identification
61            trustProxy: ['127.0.0.1', '::1']
62        },
63
64        // Configure which files and directories starting with a dot (.) can be served.
65        // The following example shows the default configuration - '/.well-known/' is
66        // already included by default, so you only need to specify this option if you
67        // want to add additional paths or remove the default.
68        dotPrefixes: ['/.well-known/']
69    })
70});

Configuration

The configuration documentation can be found here: https://friedemannsommer.github.io/astro-node-fastify/.

Troubleshooting

Common Issues and Solutions

Compression Not Working

Symptoms: Assets aren't being compressed as expected, or browsers aren't receiving compressed content.

Solutions:

• Make sure you haven't disabled preCompressed if you want build-time compression
• Check that your supportedEncodings includes the compression algorithms you expect (br and/or gzip)
• Verify that the client sending requests includes the appropriate Accept-Encoding header

404 Errors for Assets in Dot Files/Directories

Symptoms: Assets under directories that start with a dot (e.g., .github/) are inaccessible.

Solutions:

• Add the path prefix to the dotPrefixes option (e.g., ['/.custom-directory/', '/.other-directory/'])
• Note that by default only /.well-known/ is allowed

Static Assets Not Caching Properly

Symptoms: Browsers repeatedly download the same static assets instead of using cached versions.

Solutions:

• Ensure your cache configuration is correctly set with appropriate values
• Check if other headers in your deployment environment (like CDN settings) might be overriding your cache configuration
• Verify that the Cache-Control header is being set correctly using browser developer tools

Server Running Out of Memory

Symptoms: Server crashes with memory-related errors under load.

Solutions:

• Consider setting preCompressed: true (default) to avoid runtime compression overhead
• If your site has huge assets, you might need to allocate more memory to your Node.js process

Issues Behind a Reverse Proxy

Symptoms: Client IP addresses are incorrect, or some security features don't work properly.

Solutions:

• Configure the server.trustProxy setting to properly identify trusted proxy servers
• Ensure your reverse proxy (nginx, Apache, etc.) is correctly configured to pass the required headers:
  • X-Forwarded-For: Original client IP address
  • X-Forwarded-Proto: Original protocol (http/https)
  • X-Forwarded-Host: Original host requested by the client
  • X-Real-IP: Alternative client IP header used by some proxies

Getting Help

If you encounter issues not covered here:

1. Check the GitHub Issues to see if your problem has been reported
2. Before opening a new issue:
   • Make sure the issue is related to this adapter specifically, not your Astro project or deployment environment
   • Create a minimal reproduction that isolates the problem to this adapter's functionality
   • Include your adapter configuration and relevant environment details (Node.js version, OS, etc.)

Support Scope:

• ✅ Issues with the adapter's core functionality (compression, serving files, caching, etc.)
• ✅ Documentation clarifications or improvements
• ✅ Feature requests specific to the adapter
• ❌ General Astro project issues not specific to this adapter
• ❌ Deployment environment setup (AWS, Vercel, etc.)
• ❌ Custom server configurations beyond this adapter's API

For general Astro help, please use Astro's Discord or Stack Overflow.