-
-
Notifications
You must be signed in to change notification settings - Fork 17
feat!: archive @ryoppippi/unplugin-typia
#500
Conversation
|
Warning Rate limit exceeded@ryoppippi has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 11 minutes and 4 seconds before requesting another review. β How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. π¦ How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. π Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. πͺ§ TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @ryoppippi, I'm Gemini Code Assist1! 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!
I've created this pull request to formally announce the archiving of the unplugin-typia project. The main change involves updating the README.md to provide detailed context, explain the reasons behind the decision (technical shifts in TypeScript and personal focus), highlight the project's impact, and offer guidance for existing users regarding technical status and alternatives.
Highlights
- Reasons for Archiving: The decision is primarily driven by technical uncertainty regarding TypeScript's ongoing migration to
tsgo(a native Go port) which changes compiler internals access, and a shift in my personal project focus. - Project Impact & Adoption: The plugin achieved significant adoption, being used in notable projects like Hugging Face Inference Playground and Wrtn Labs Agentica, and consistently maintained over 22K weekly downloads on npm.
- Technical Status & Alternatives: The current version should remain functional as long as Typia's transformation approach and bundler/TypeScript compatibility hold. Users needing continued support are encouraged to fork the repository or explore Typia's official built-in integrations or generation mode.
- Acknowledgments: I've expressed gratitude to sponsors (@samchon, @timoxley) and the broader community for their support, contributions, and adoption, reflecting on the valuable technical and personal growth gained from the project.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| 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 issue 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 is currently in preview and 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 to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. β©
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the README to announce the archiving of the unplugin-typia repository, providing context, its current impact, and guidance for users moving forward.
- Announces the archiving of unplugin-typia and explains the technical and personal reasons behind the decision
- Highlights the plugin's adoption in notable projects and provides instructions on alternatives for continued support
- Includes technical status updates and acknowledgments for contributors
commit: |
@ryoppippi/unplugin-typia
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request effectively communicates the archival of the unplugin-typia repository by replacing the root README.md with a comprehensive announcement. The new content clearly outlines the reasons for archiving, the project's significant impact and adoption, its current technical status, potential alternatives for users, and heartfelt acknowledgments. The information is well-structured and thoughtfully presented.
My review includes one comment on the README.md file concerning a minor inconsistency in the stated timing of the archival, with suggestions for clarification. Overall, the changes achieve the goal of informing the community about the repository's new status.
π¦ Archiving unplugin-typia
After two years of development and community support, I'm archiving this repository effective immediately.
π― TL;DR
This plugin will no longer be maintained. Feel free to fork if you need continued support.
π Background
unplugin-typiawas created to make [Typia](https://typia.io) integration easier across different bundlers like Vite, esbuild, Webpack, and others. It has served its purpose well, but several factors have led to this decision:Technical considerations: TypeScript's ongoing migration to [tsgo (TypeScript Native Port)](https://devblogs.microsoft.com/typescript/typescript-native-port/) introduces significant architectural changes. The new Go-based compiler uses IPC-based APIs rather than direct access to compiler internals, creating uncertainty around transformation tools like Typia and ts-patch that rely heavily on TypeScript's internal APIs.
Personal transition: My focus has shifted to other projects and directions.
π Adoption & Impact
I'm incredibly proud that this plugin found its way into many notable projects:
The plugin has consistently maintained 22K+ weekly downloads on npm, demonstrating real community value and adoption.
π§ͺ Technical Status
The current codebase should continue working as long as:
tsc+ts-patchbased transformation approachYou may need to update peer dependencies over time, but the core transformation mechanism should remain stable until TypeScript's architectural changes take effect.
π Alternatives
Currently, there's no direct replacement. If you need continued support:
π Acknowledgments
This journey wouldn't have been possible without incredible support:
@samchon was my first sponsor and provided the opportunity to contribute significantly to Typia's development. My research and optimization work helped improve Typia's performance and led to detailed technical blog posts that resonated strongly with the community.
@timoxley became a sponsor after seeing this project's impact, providing additional encouragement for open-source work.
The broader TypeScript and bundling community embraced this tool, and seeing it used in production at companies and significant open-source projects has been incredibly rewarding.
Working on this project deepened my understanding of build systems, tree-shaking, TypeScript transformations, and compiler optimization techniques. The technical challenges and solutions developed here have been invaluable for my growth as a developer.
π Looking Forward
While I'm stepping away from this specific project, I wish the Typia community continued success. The innovations in TypeScript runtime validation and serialization that Typia pioneered have pushed the entire ecosystem forward.
Thank you to everyone who used, contributed to, or supported this project. Your feedback and adoption made this journey meaningful.
Repository archived on June 14, 2025