fix(media): component failing when setting a custom serverURL

[dsm23]

• templates: fix Media component failing when setting a custom serverURL payloadcms/payload#12214

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[github-actions]

📦 Next.js Bundle Analysis for dsm23-next-payloadcms-postgres-template

This analysis was generated by the Next.js Bundle Analysis action. 🤖

Six Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load
/(frontend)/[slug]/page	94.19 KB (🟢 73 B)	194.66 KB
/(frontend)/page	94.19 KB (🟢 73 B)	194.66 KB
/(frontend)/posts/page	23.55 KB (🟢 60 B)	124.02 KB
/(frontend)/posts/[slug]/page	49.03 KB (🟢 73 B)	149.5 KB
/(frontend)/search/page	22.53 KB (🟢 72 B)	123 KB
/(frontend)/posts/page/[pageNumber]/page	23.55 KB (🟢 60 B)	124.02 KB

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by undefined% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

[mergify]

Automatically approving dsm23