The base flag from the astro config is ignored completely

[feldspar9s]

Description

astro-sst should consume the base flag specified in the astro.config.mjs file and use it to determine the subdirectory/prefix of the static assets in the s3 bucket, as well as the pathPattern for both the regionalServer and the staticServer.

---

Current Behavior

The base flag in the astro config is ignored while the static assets are pushed to s3, and when the behaviors are added to cloudfront

• Example astro.config.mjs file:

// @ts-check
import { defineConfig } from 'astro/config';
import aws from "astro-sst";

export default defineConfig({
 output: "server",
 base: '/home',
 adapter: aws()
});

• The resulting s3 keys :

bucket_root
├── _astro/*
├── favicon.svg
└── index.html

• The resulting cloudfront behaviors

Origin	Path Pattern
staticsServer	_astro/*
regionalServer	_image

---

Expected Behavior

The base flag should be used to prefix both the object keys in s3 and the pathPatterns in cloudfront

• Expected s3 keys:

bucket_root
├── home
│   ├── _astro/*
│   ├── favicon.svg
└   └── index.html

• Expected cloudfront behaviors:

Origin	Path Pattern
staticsServer	/home/_astro/*
regionalServer	/home/_image

---

Details

• Tested on: 10th Jan 2025
• Astro version : 5.1.3
• astro-sst version: 2.45.2
• sst version: 3.5.3