Compatibility Date warning on non-cloudflare environments

[ssahillppatell]

Environment

bun: v1.1.38
nitropack: latest

Reproduction

Steps:

1. bunx giget@latest nitro nitro-app --install
2. bun run dev

Describe the bug

When trying to run the server using Bun, I get a warning asking me to state a compatibility date, which I do not wish to add to my config.
According to this doc. I must only mention the compatibility date on the Cloudflare worker environment.

Am I missing something?? Is this supposed to happen?

Additional context

No response

Logs

WARN  No valid compatibility date is specified.                                                                                                                          

❯ Do you want to auto update config file to set compatibilityDate: '2024-12-01'?
● Yes / ○ No

[gxres042]

This configuration is used to control the behavior of Nitro.

You may need to confirm whether your current environment requires this configuration.

[ssahillppatell]

My current environment shouldn't require a compatibility date. As I mentioned in the issue description, I get a warning when running a new nitro project, which should differ from the case as I am not using Cloudflare workers.
It should just run like any new express project without warning for a not-required configuration.

[gxres042]

This configuration is used to control the behavior of Nitro.

cc @pi0: I think we can add a default compatibility date into configuration file.

[TheAlexLichter]

Compatibility date is e.g. used to for behavior changes of providers (think of e.g. the vercel or CF preset having a breaking change) without pushing a new major version all the time for these changes. Also talked about it here.