Extended configurations do not respect `skipValidation`

[oswaldoacauan]

I would expect that when extending a preset it would respect the skipValidation flag of where it was extended, instead it only follows the preset skipValidation configuration.

// packages/auth/env.ts
import { createEnv } from "@t3-oss/env-core";
export const env = () => createEnv({
  // no skipValidation set
});
 
// apps/web/env.ts
import { createEnv } from "@t3-oss/env-nextjs";
import { env as authEnv } from "@repo/auth/env";
 
export const env = createEnv({
  // ...
  extends: [authEnv()],
  skipValidation: !!process.env.SKIP_ENV_VALIDATION,
});

For the code above I would expect that if SKIP_ENV_VALIDATION=true all validations will be skipped, but thats not the case, the validations for /packages/auth/env.ts will still run.

To fix it, I need to replicate the skipValidation: !!process.env.SKIP_ENV_VALIDATION, on each of my presets.

Demo: https://codesandbox.io/p/devbox/7jhxrg

Is this the expected behaviour? It probably should be mentioned at least somewhere in the docs that presets are fully independent configurations and that they run in a standalone mode regardless of the options of where they were extended.

[OreQr]

If someone is using Typescript, for now you can create object that gonna contain shared options like this:

export const sharedEnvOptions = {
  emptyStringAsUndefined: true,
  skipValidation: !!process.env.CI || !!process.env.SKIP_ENV_VALIDATION,
} satisfies Partial<Parameters<typeof createEnv>[0]>

export const someEnv = createEnv({
  ...,

  ...sharedEnvOptions,
})

[Bartek532]

Hey!

I just released a library that might be a great fit for your use case - it's a drop-in replacement for the one you're currently using, with some extra features like a built-in CLI and live preview:

🔗 https://envin.turbostarter.dev/

Feel free to reach out if you have any questions or suggestions - every bit of feedback is welcome! 🔥