Feature Request: Override process.env By Auto Generating Type Definitions From .env Files

[barziahmed]

Currently, expo-modules-core, a package from One project, overrides and uses its own type definition as ExpoProcess for process.env, it should be prevented from doing so and One implements type definitions by itself from env files.

[natew]

As a workaround until this is implemented, you can manually create a type definition file for your environment variables:

// env.d.ts
declare namespace NodeJS {
  interface ProcessEnv {
    API_URL: string
    NODE_ENV: 'development' | 'production' | 'test'
    // Add your env vars here
  }
}

For auto-generation, there are community packages like dotenv-cli with type generation, or you could use a build script that reads your .env file and generates the types.

This feature request is valid - auto-generating types from .env files would improve DX.