Pooya Parsa

js runtime support depends on drivers (if they support broeser they do) — we shouldn’t make an exception entey for browser. re parsing, it kinda makes sense for some drivers...

that's a bundler-specific config people should do. Also, we need to have **exactly** syntax below in the generated list: ```js () => import("unstorage/drivers/name") ``` this is because when using `import(unstorage/drivers/${name})`...

It is under my track. https://github.com/SuperchupuDev/tinyglobby/pull/70 has not been solved yet (without it, users cannot ignore some public paths)

Users should be able to ignore specific FS scan patterns and public assets. This was a feature Nitro (and Nuxt by using Nitro) always had and certainly users are depending...

This is good for `nitro@3` which will be available in the upcoming Nuxt major version 👍🏼 (removed covering feature: https://github.com/nitrojs/nitro/pull/3257/commits/4fbd74e0e4fb5486b6d406ebe4d07c0c2b6c068f) --- To backport `nitropack@2`, we need negate support and avoid...

Let's track progress support via #45

Nitro supports `vfs` option for virtual templates have you tried it? what missing features would new templates add?

Thanks for the explanation. I think we need to make the API more relevant to generated types then, not confusing with virtual source files.

not planned for now and can be done in userland for actually writing custom files to the filesystem. Two core functions: - VFS to extend virtual importable files - Typegen...

Porting to v3 might be better, specially because now route rules are tree-shakable (and extendable by addition option soon!)