Revive removed fedify init options

[2chanhaeng]

Summary

Revive removed fedify init options.

• In-memory in Message Queue.
• In-process in KV Stores.
• Bare-bones in Web Frameworks.

Related issue

• closes Revive removed fedify init options #632

Changes

• packages/init/src

Benefits

Now users can use the options again.

Checklist

• Did you add a changelog entry to the CHANGES.md?
• Did you write some relevant docs about this change (if it's a new feature)?
• Did you write a regression test to reproduce the bug (if it's a bug fix)?
• Did you write some tests for this change (if it's a new feature)?
• Did you run mise test on your machine?

Additional notes

In version 2.1, since the webframeworks.ts file is modularized by framework, some modifications are required.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the fedify init command by reintroducing several previously removed options. Users can now select 'bare-bones' for web frameworks, 'in-memory' for key-value stores, and 'in-process' for message queues, providing more lightweight and flexible initialization choices, particularly useful for development and testing. The changes also include necessary documentation updates, refactoring of configuration constants, and the addition of new templates to support these revived options.

Highlights

• Revived fedify init options: The previously removed bare-bones option for web frameworks, in-memory for key-value stores, and in-process for message queues have been reinstated, offering more flexibility during project initialization.
• Updated documentation: The CLI documentation and the init package README have been updated to accurately reflect the availability of these re-added options.
• Dynamic constant loading: The MESSAGE_QUEUE and KV_STORE constants are now dynamically loaded from dedicated JSON files, improving maintainability and extensibility.
• New bare-bones templates: New template files have been added to support the bare-bones web framework option across different runtimes, including Bun, Deno, and Node.js.
• Conditional dependency handling: Logic was introduced to prevent the addition of @fedify dependencies for 'no integration' options like in-memory, in-process, and bare-bones.
• Improved test utility: The lookup.ts test utility was enhanced to gracefully handle server port determination failures by falling back to a default port.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request successfully revives the bare-bones web framework, in-memory key-value store, and in-process message queue options for fedify init. The changes include updating documentation, introducing new configuration JSON files for KV stores and message queues, and adding corresponding bare-bones templates for Deno, Bun, and Node.js. The dynamic loading of KV and MQ options from JSON files is a good architectural improvement, centralizing configuration. Additionally, the test suite has been made more robust by incorporating default port fallbacks.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[dahlia]

Good job!