feat(astro-redirects): Astro integration for _redirects and frontmatter redirects

[pcfreak30]

Summary

Astro integration that generates redirects from _redirects files, Markdown frontmatter, and programmatic config. Compatible with the IPFS Web Redirects File spec and inspired by astro-redirect-from.

Features

• Parse _redirects files (Netlify/IPFS spec):
  • Splats (*), placeholders (:id)
  • Status codes: 200, 301-308, 404, 410, 451
  • 64 KiB file size limit
• Extract redirect_from from Markdown/MDX frontmatter via gray-matter
• Skip draft: true posts in production builds
• Optional emitFile to output _redirects text for static hosts
• Extra static redirects via config

Usage

import redirects from '@lumeweb/astro-redirects';

export default defineConfig({
  integrations: [
    redirects({
      redirectsFile: true,
      frontmatter: true,
      emitFile: true,
      extra: { '/old': '/new' },
    }),
  ],
});

Package

• libs/astro-redirects/ — new workspace package
• private: true for now until ready to publish
• 100% test coverage (25 tests)

Files Changed

• libs/astro-redirects/* — new package (12 files)
• pnpm-lock.yaml — gray-matter + deps

---

This pull request introduces a new @lumeweb/astro-redirects Astro integration library that centralizes redirect management for Astro-based projects.

The integration collects redirect rules from three sources:

1. _redirects files (Netlify/IPFS Web Redirects format) located in the public directory or a custom path
2. redirect_from frontmatter in Markdown/MDX content files under src/pages
3. Additional static or dynamic redirects supplied via plugin configuration

Supported capabilities include splat patterns (*), dynamic placeholders, common HTTP status codes (200, 301–308, 404, 410, 451), and absolute destination URLs with allowed schemes (http, https, ipfs, ipns).

The integration registers valid 3xx redirects with Astro's built-in redirect config and can optionally emit a _redirects text file into the build output for deployment to static hosts. Draft content is excluded from production builds.

The change adds the full library source, unit tests, build configuration, documentation, and updates the lockfile with the new package dependencies.

[kody-ai]

Found critical issues please review the requested changes

• Recursive markdown collection has no cyclic-symlink guard and can loop forever.

[kody-ai]

Found critical issues please review the requested changes

• _redirects file is loaded into memory before the 64 KiB size limit is enforced.

[kody-ai]

Found critical issues please review the requested changes

• Symlinked markdown files bypass the contentDir traversal guard and can read arbitrary files outside the directory.

[kody-ai]

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.

​