
Security News
arXiv Is Rate Limiting Authors Following a Flood of AI Slop Submissions
arXiv now limits authors to two submissions a month as AI slop overwhelms moderators, delays good papers, and sparks debate over applying the limit to everyone.
@fedify/astro
Advanced tools
AstroThis package is available since Fedify 2.1.0.
This package provides a simple way to integrate Fedify with Astro.
First, add the integration to your astro.config.mjs:
import { defineConfig } from "astro/config";
import { fedifyIntegration } from "@fedify/astro";
export default defineConfig({
integrations: [fedifyIntegration()],
output: "server",
});
Then, create your middleware in src/middleware.ts:
import { createFederation } from "@fedify/fedify";
import { fedifyMiddleware } from "@fedify/astro";
const federation = createFederation<void>({
// Omitted for brevity; see the related section for details.
});
export const onRequest = fedifyMiddleware(
federation,
(context) => void 0,
);
If you are using Deno, you should import @deno/vite-adapter in
astro.config.mjs and use it as the adapter:
import { defineConfig } from "astro/config";
import { fedifyIntegration } from "@fedify/astro";
import deno from "@deno/vite-adapter";
import deno from "@deno/astro-adapter";
export default defineConfig({
integrations: [fedifyIntegration()],
output: "server",
adapter: deno(),
});
And the tasks in deno.json should be updated to use deno run npm:astro
instead of astro:
{
"tasks": {
"dev": "deno run -A npm:astro dev",
"build": "deno run -A npm:astro build",
"preview": "deno run -A npm:astro preview"
}
}
Fedify behaves as a middleware that wraps around the Astro request handler.
The middleware intercepts the incoming HTTP requests and dispatches them to
the appropriate handler based on the request path and the Accept header
(i.e., content negotiation). This architecture allows Fedify and your Astro
application to coexist in the same domain and port.
The fedifyIntegration() function configures Vite's SSR settings to ensure
that @fedify/fedify and @fedify/vocab are properly bundled during SSR.
For example, if you make a request to /.well-known/webfinger Fedify will
handle the request by itself, but if you make a request to /users/alice
(assuming your Astro app has a page for that path) with
Accept: text/html header, Fedify will dispatch the request to Astro's
page handler. Or if you define an actor dispatcher
for /users/{identifier} in Fedify, and the request is made with
Accept: application/activity+json header, Fedify will dispatch the request
to the appropriate actor dispatcher.
deno add jsr:@fedify/astro # Deno
npm add @fedify/astro # npm
pnpm add @fedify/astro # pnpm
yarn add @fedify/astro # Yarn
bun add @fedify/astro # Bun
FAQs
Integrate Fedify with Astro
The npm package @fedify/astro receives a total of 2,867 weekly downloads. As such, @fedify/astro popularity was classified as popular.
We found that @fedify/astro demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.

Security News
arXiv now limits authors to two submissions a month as AI slop overwhelms moderators, delays good papers, and sparks debate over applying the limit to everyone.

Research
/Security News
A new GhostAction wave hits hundreds of GitHub repos, expanding CI/CD secret theft to cloud and AI credentials in source code and git history.

Research
/Security News
Tensorlake npm SDK version 0.5.144 was compromised in a ChainDrop / Shai-Hulud attack, delivering credential-stealing malware.