bun-env-file-for-dev

What problem does it solve?

Bun runtime does not automatically load .env files during local development, unlike Node.js, leading to undefined environment variables for dependent tools and services. This causes silent failures or obscure errors for AWS SDK calls, Prisma database operations, and boot-time secret validation in Bun dev servers.

Core Features & Use Cases

• Provides the correct Bun startup command with the --env-file flag to load .env variables properly
• Resolves AWS SDK v3 region and credential errors caused by missing environment variables in local development
• Fixes edge cases including Prisma seed scripts not inheriting parent process env flags, current working directory path traps for .env loading, and boot-time secret testing pitfalls
• Use Case: A developer building a Bun backend with AWS SES integration can use this skill to ensure SES region and credential env vars load correctly, so email sending works in local dev without 500 errors.

Quick Start

Use this skill to fix undefined environment variable errors in your Bun dev server by applying the correct --env-file flag to your startup command, ensuring AWS SDK and other dependent tools work properly in local development.