fedify-dev/fedify

AI Summary: The `@fedify/nestjs` package currently restricts its `express` peer dependency to version `^4`, causing conflicts with NestJS 11 projects which now use Express 5 by default. This issue tracks updating the peer dependency range in `@fedify/nestjs` to include Express 5, resolving compatibility warnings and allowing seamless integration with NestJS 11.

AI Summary: The task involves systematically replacing all instances of the incorrect JSDoc tag `@typeParam` with the correct `@template` tag in the Fedify TypeScript codebase. This is a documentation-only change affecting all files containing generic types and functions, impacting documentation generation, IDE support, and developer experience.

AI Summary: The task is to improve the Fedify CLI's dependency management. Currently, dependencies are hardcoded; the goal is to dynamically fetch the latest versions of these dependencies, leveraging the monorepo structure for Fedify packages and using static imports for version information to ensure compatibility with the executable build process. The `logtape` dependency will require manual updates.

AI Summary: Add a `--max-redirection` command-line option to the `fedify webfinger` command, mirroring the existing `maxRedirection` option in the WebFinger lookup API. This involves modifying the `cli/webfinger.ts` file to accept the new option, validate its input, and pass it to the `lookupWebFinger()` function.

AI Summary: Debug and fix a `TypeError: unusable` error in the Fedify ActivityPub server framework, specifically within the double-knock authentication process. The error seems to originate from the `undici` HTTP client library when handling requests that result in 4xx or 5xx responses. The task involves analyzing Sentry error reports, examining the `signRequest` and `doubleKnock` functions in the `http-D2kxx0MM.js` file, and potentially modifying the request handling to gracefully manage non-2xx responses from the server.

AI Summary: Update the project's README file to reflect the change in the documentation build process from using Bun to using Node.js with pnpm. This involves replacing the outdated Bun commands with the correct pnpm commands.

AI Summary: Develop a TypeScript package, `@fedify/backfill`, for Fedify, an ActivityPub server framework. This package will implement conversation backfilling using multiple strategies: prioritizing FEP-f228's context owner approach, falling back to reply tree crawling, and optionally offering a hybrid approach. The package should be efficient, handle errors gracefully, and integrate seamlessly with existing Fedify applications.

AI Summary: Integrate the Fedify ActivityPub server framework with the NestJS framework. This involves creating a NestJS module that utilizes Fedify's functionalities, likely requiring careful consideration of data structures and API interactions to ensure seamless communication between the two frameworks.

AI Summary: Implement a new `fedify webfinger` CLI command that performs isolated WebFinger lookups, taking a handle as input and outputting the JRD in JSON format. This involves creating a new `webfinger.ts` file in the CLI directory, leveraging existing Fedify functions, and registering the command in `mod.ts`. Error handling and clear output are crucial.

AI Summary: Rename the `fedify node` command-line interface (CLI) command to `fedify nodeinfo` to better reflect its function of interacting with the NodeInfo protocol, improving clarity and consistency with the specification.

AI Summary: Enhance the `fedify node` command-line tool to support outputting NodeInfo data in JSON and compact JSON formats, in addition to the existing human-readable format. This involves adding `--json` and `--compact` flags to the command, updating the help text, and handling potential errors during data retrieval.

AI Summary: Implement a `--output` option for the `fedify lookup` CLI command to save results to a file. This involves modifying the `lookup.ts` file to add the option using cliffy, handle file writing using `Deno.writeTextFile()`, manage potential errors, and update the help text. The solution should maintain compatibility with existing formatting options.

AI Summary: Enhance the `fedify inbox` command-line tool to accept optional parameters (`--actor-name` and `--actor-summary`) for customizing the temporary actor's name and summary during testing. This involves modifying the `cli/inbox.tsx` file to use the `cliffy` library for option parsing, updating the `Application` object creation to use these custom values, and adding appropriate default values and help text.

AI Summary: Implement a `--dry-run` option for the `fedify init` command. This involves modifying the `cli/init.ts` file to add the flag using cliffy, conditionally write files to disk, and output file paths and contents to the console when the flag is used. The output should clearly distinguish between different files. Existing functionality must be preserved when the flag is not used. The command help text needs updating to document the new option.

AI Summary: Implement a `--timeout` option for the `fedify lookup` command in the Fedify TypeScript project. This involves adding the option to the CLI, updating the document loader to use `AbortController` for timeout handling, and improving error messages. The implementation should be compatible with existing functionality and handle both single and multiple URL lookups, including the `--authorized-fetch` and `--traverse` options.

AI Summary: Implement a check in the Fedify CLI to disable color output if the standard output is not a TTY (terminal), ensuring compatibility with redirected output and preventing issues with tools like `grep` or `less`. This involves using `Deno.stdout.isTerminal()` to detect the output type and conditionally applying color codes.

AI Summary: Investigate and fix a bug in the Fedify documentation search functionality where search results are broken for headings containing code blocks. The issue appears to be related to how the search engine handles headings with embedded code, not necessarily a problem within Fedify itself. The fix likely involves adjusting the search indexing or query processing to correctly handle code blocks within headings.