Unclear documentation for the Additional Features page

[StVladyslav]

Describe the bug
Unclear documentation for the Additional Features page.

Steps to reproduce
The page mentions that user can 'Add additional D1 databases, R2 buckets (blob), KV namespaces & analytics datasets' but actually there's no possibility to add an additional binding for d1 database.

Expected behavior
Remove the text with states that additional bindings can be used to add additional D1 databases, or provide a way to add additional d1 bindings. Because d1 type cannot be specified in config, like

      d1:
        {
          binding: 'DB',
          database_name: 'test',
          database_id: '00000000-0000-0000-0000-000000000000',
        },
    },

but it says Refer to Cloudflare's API documentation to see a list of binding type names under bindins. And d1 type is listed there.

Please clarify, maybe I got something wrong.

[RihanArfan]

Thanks for raising the issue. I've checked and while the types are missing for D1's bindings, NuxtHub will still apply them despite the type error.

core/src/types/module.ts

Lines 281 to 283 in abe1a07

	type ProhibitedBindingTypes = 'ai' | 'assets' | 'browser_rendering' | 'vectorize'
	export type AdditionalCloudflareBindings = WorkersBindingKindAnalyticsEngine | WorkersBindingKindDispatchNamespace | WorkersBindingKindJson | WorkersBindingKindMTLSCERT | WorkersBindingKindPlainText | WorkersBindingKindQueue | WorkersBindingKindService | WorkersBindingKindTailConsumer | WorkersBindingKindVersionMetadata

The correct syntax to add additional D1 bindings in production with NuxtHub is as follows. You can use this, despite the type error which we'll sort soon.

      d1: {
        DB2: { // DB is reserved and used by NuxtHub
          id: '<D1_ID>'
        }
      }

This is from the docs, and the type and name of the additional binding are set via the d1: {} and DB2 parts of the NuxtHub config.

[Alecyrus]

Hi @RihanArfan, could you please help with this issue regarding additional R2 bindings in NuxtHub?
As described in #655, configuring extra R2 buckets in hub.bindings.r2_bucket does not expose the R2 binding in event.context.cloudflare.env after deployment—only CACHE appears.
Is there any workaround, or could you clarify the correct approach for binding multiple R2 buckets in NuxtHub?
Thanks in advance!

[StVladyslav]

@RihanArfan Thank you for the detailed response — I’ll give it a try. I have one additional question: what is the recommended way to access DB2 from the code? For example, will it be available through something like event.context.cloudflare.env.DB2, similar to Nitro bindings? Also, would this approach work correctly in combination with Durable Objects?
Thanks in advance!