Last 12 weeks · 2 commits
2 of 6 standards met
Related #118 This PR removes the fallback behavior that was triggered when the specified package manager was not found. The fallback make it difficult for users to debug issues, and given that this tool may be executed by AI agents, it should fail explicitly rather than silently falling back to an interactive TUI prompt.
Repository: honojs/create-hono. Description: CLI for creating a Hono app Stars: 104, Forks: 21. Primary language: TypeScript. Languages: TypeScript (99.7%), JavaScript (0.3%). License: MIT. Latest release: v0.19.4 (2mo ago). Open PRs: 1, open issues: 9. Last activity: 4d ago. Community health: 37%. Top contributors: yusukebe, ryuapp, MathurAditya724, ryoppippi, 6km, jculvey, arturgawlik, blazeshomida, emmanuelchucks, BRAVO68WEB and others.
The link to LICENSE was broken, so I removed it and created the license to this repo. It inherits the license as of create-solid v0.2.12. That version references the date in the commit history: https://github.com/honojs/create-hono/commit/5c5fa4398ce509f14a2a254901cf5e32d172e97d
HonoX is currently under active development, and its README explicitly states that breaking changes may be introduced. If a user starts their project using the template and later breaking changes are made to HonoX, users who do not properly manage lock files may be confused by changes in HonoX's behavior. To avoid this confusion, I suggest updating the in the section of to , thereby pinning the version. What do you think about this approach? We could simply change the template, or alternatively, consider pinning the version as a post-processing step in .