Provide a CLI for per-hook installation for customizability

[cstayyab]

Summary

Introduce a Shadcn-inspired command-based hook installation for usehooks-ts, enabling developers to add individual hooks with a single command (e.g., npx usehooks-ts add useInterval). This approach enhances customizability by allowing developers to selectively install and modify only the hooks they need, directly within their project’s codebase.

Motivation

usehooks-ts is a powerful library, yet developers sometimes only need a few hooks or may wish to adjust specific logic within these hooks to align with unique project requirements. Currently, installing the full package or managing custom changes in a separate repository can be cumbersome. A command-based installation system—similar to Shadcn’s component addition—would allow developers to add and customize individual hooks on demand, directly into their project structure.

Proposed Solution

1. Command-Line Installation:

   • Implement a CLI command (e.g., npx usehooks-ts add <hook-name>) to allow developers to add individual hooks to their project. For example:

     npx usehooks-ts add useInterval

   • This command would:
     • Download the specific hook’s code and dependencies.
     • Add the selected hook as a new file (or set of files) within the developer's project, making it directly available for customization.

2. CLI Structure and Workflow:

   • The npx usehooks-ts CLI tool would fetch the latest version of the selected hook from the usehooks-ts repository.
   • Each hook would be designed as a standalone file, with any shared utilities or types added automatically if they aren’t already present.
   • This CLI would support updating existing hooks, ensuring developers maintain flexibility while staying current with the latest library improvements.

3. Documentation and Usage:

   • Update documentation to include a new section on installing hooks via npx usehooks-ts add <hook-name>.
   • Each hook’s documentation would describe any customization options or dependencies, giving developers insights into adapting the hook to fit project-specific needs.

4. Codebase Refactoring:

   • Refactor usehooks-ts to provide each hook as a standalone file or module. This modular setup would enable the CLI tool to fetch and install only the requested hook, similar to the approach in Shadcn’s system.

Benefits

• High Customizability: Developers can add individual hooks to their project and modify them as needed, directly within their codebase.
• Simplified Workflow: The single-command installation reduces friction by making individual hooks readily accessible and easy to customize.
• Future-Proof: Developers can easily update specific hooks as new versions are released, maintaining flexibility and ensuring compatibility with the latest library updates.

Considerations

1. Initial Setup and CLI Development: Implementing the CLI and adjusting the repository structure for modular hook delivery will require initial setup time.
2. Maintaining Version Consistency: Ensuring that hooks pulled into a project remain compatible with shared dependencies or utilities may require careful management.
3. Documentation and Updates: Documentation will need updates to explain the command structure, along with customization guidance for each hook.

---

This approach could bring usehooks-ts a significant boost in usability and customizability, enabling developers to easily tailor hooks to their unique needs without managing complex forks.