Meta: monorepo maintenance

[BarryThePenguin]

Hi 👋🏻 would the Hono devs be interested in reviewing contributions to the configuration and maintenance of the monorepo? Some ideas I have include..

• Investigate migrating workspaces that use jest to vitest #994
• use unplugin-typia in @hono/typia-validator tests #999
• Remove vitest-environment-miniflare #1003
• vitest.workspace #1007
• setup test.coverage for Vitest
• workspaces
• Use Bun as package manager #628
• upgrading eslint plugins
• removing @eslint/eslintrc and the legacy FlatCompat
• cleanup migration to typescript-eslint
• align build/test/prerelease/release scripts in workspaces
• include @arethetypeswrong/cli in the publish/release process
• cleanup duplicate dependencies between workspaces

I'm happy to volunteer, I'll aim to keep changes small and focused. I'm just gauging the interest of others to review the changes, and if these kinds of changes would be useful for the project 👀

[yusukebe]

Hi @BarryThePenguin !

I am super interested in your proposal! The maintainability will be greatly improved.

All 5 thins you picked up are good to do. Regarding monorepo, we were discussing moving package manager to Bun and using Bun's workspace. #628

It may be good to start with migration using Bun.

cc: @gunta @nakasyou

[nakasyou]

That's a good idea! However to use Bun, we need to match all packages with the latest Hono.

[yusukebe]

However to use Bun, we need to match all packages with the latest Hono.

This will be a pain point. Ideally, all packages should pass the test using the latest version of Hono, but I think that's difficult.

It might be better to continue using yarn. We could use pnpm, but since we don't use it in any of the other projects in honojs, I think it's fine to use yarn.

[BarryThePenguin]

Ok, I think sticking with yarn for the short term would work best. With a longer term goal of adopting bun, once some of the more pressing maintenance issue have been resolved.

However to use Bun, we need to match all packages with the latest Hono.

I'll keep this in mind 👍🏻

[yusukebe]

@BarryThePenguin Thanks! Can you proceed with it?

[BarryThePenguin]

Sure thing 👍🏻 I'll start with #994, then I'll look at what is involved in enabling vitest.workspace.

Please feel free to add/remove/rearrange items in the list above and I can work through them as I have time

[yusukebe]

@BarryThePenguin Thaaaanks!

[MathurAditya724]

Hey, @BarryThePenguin, I was thinking of working on the ESLint part of the repo. If no one else is working on it, I can start creating a PR for it.

[BarryThePenguin]

Hi @MathurAditya724, sounds good! 👍🏻