Pooya Parsa

It is a really nice idea. I suggest `meta.unimport: "dist/unimport.json"` convention for `package.json` (or a nested object if fits better) points: - Consumer tooling can do a cheap analyze to...

Using `exports` field of package.json simplifies library setup indeed but also I see some downsides for consumer/tooling part affecting perf of end user. Bundlers, often already scan `package.json` in their...

What if we instead support `defineRoute({ middleware: true, ... })`? Most of spec looks similar other than it would call `app.use` instead of `app.on`

It is `{ definePlugin } from "nitro"`, likely it will be `from "nitro/define"` in next alphas.

Thanks for the explanations, @pan93412 ❤️. It makes sense if the platform is simplified by switching to a `node-server`–style preset that also works with Dockerfile templates. My concern is that...

Some providers also detect "some" Nitro based frameworks however zero config detection build output and docs are based on assumption that platform's framework detection is not a hard requirement. Maintaining...

It is possible to pass the full path to drivers by setting `driver` to the absolute path of a custom driver ([v2 src](https://github.com/nitrojs/nitro/blob/c2d08819eb91f6a3004f4fab184b1cc3151d9acc/src/rollup/plugins/storage.ts#L21), [v3 src](https://github.com/nitrojs/nitro/blob/9b276e11d3a4e275ae1eca765d1621c85d9b2c0a/src/build/virtual/storage.ts#L23)) **Example:** ```js export default defineNuxtConfig({...

This looks fine!

We need to first make `scanAndSyncOptions` side-effect free (TODO [in src](https://github.com/nitrojs/nitro/blob/046a8c291a84f6f75e294b2ec8ee30aaa42d0014/src/core/nitro.ts#L40-L42)) Also we need to make a new (perhaps native) watcher instance watching top level scannable directories only for add/remove.

Can you please check the failing CI?