ryu

It's node compatibility issue for Bun, but it seems to be caused by readFileSync/writeFileSync below: https://github.com/honojs/create-hono/blob/f7ba1917bd1087c71deeea7e2a408484f08a8ba9/src/hooks/after-create.ts#L11-L16

> Does this mean "node compatibility issue for Bun on Windows"? Yes, it does. I tried the same thing in WSL but it didn't reproduce.

I had misunderstood this issue a bit. The cause was that template files could not be cloned with Bun. We could only get directories for the template. 

It's hard to support completely external community templates. `create-hono` should only support external templates that have been checked by Hono community. For those that do not apply, we will guide...

> I think we can avoid this issue if we make the create-hono change $npm_execpath to the proper package manager command. What do you think of this? Sounds nice, but...

That I could find was in overview, but it seems there are other changes as well: https://github.com/withastro/docs/commit/45a117052d85d9a706e4095f1cb9ffb2b0bf2caa 

I think this is not a bug. If I organize your code, it will look like this: ```ts import { Hono } from "hono"; const app = new Hono(); app.use(async...

It seems to be a webpack build issue. The current workaround is probably as following: ```ts // next.config.ts import type { NextConfig } from "next"; const nextConfig: NextConfig = {...

> I don't have very strong opinions, but the pro of setting it to always is that you always linebreak at 80 columns - you don't get very long lines....

> and unfortunately, some external libraries or services can sometime set exotic cookie names 😢 ...which makes the use of getCookie not ideal since it can omit a lot of...