Closes #864

Summary

Blob driver auto-detection was happening during module setup, so production Node builds baked in the filesystem driver when S3_* variables were only injected at runtime.

This defers blob driver resolution to runtime for production Node deployments, aligns the blob config types with the documented env-backed defaults, and documents the Docker/Kubernetes path.

I test it with a real docker as well

StackBlitz

CLI Reproduction

git clone --depth 1 --filter=blob:none --sparse https://github.com/onmax/repros.git
cd repros && git sparse-checkout set nuxthub-864
cd nuxthub-864 && pnpm i && pnpm build

Verify Fix

git sparse-checkout add nuxthub-864-fix
cd ../nuxthub-864-fix && pnpm i && pnpm build

The -fix folder uses pnpm patch to apply the fix locally.

Related

• S3 Blob Runtime Environment Variables not detected #864