chore: move option to baseoption (#138)

.changeset/green-terms-remain.md

@@ -0,0 +1,5 @@
+---
+"@t3-oss/env-core": patch
+---
+
+move emptyStringAsOptional to base options

packages/core/index.ts

@@ -41,6 +41,21 @@ export interface BaseOptions<TShared extends Record<string, ZodType>> {
    * @default false
    */
   skipValidation?: boolean;
+
+  /**
+   * By default, this library will feed the environment variables directly to
+   * the Zod validator.
+   *
+   * This means that if you have an empty string for a value that is supposed
+   * to be a number (e.g. `PORT=` in a ".env" file), Zod will incorrectly flag
+   * it as a type mismatch violation. Additionally, if you have an empty string
+   * for a value that is supposed to be a string with a default value (e.g.
+   * `DOMAIN=` in an ".env" file), the default value will never be applied.
+   *
+   * In order to solve these issues, we recommend that all new projects
+   * explicitly specify this option as true.
+   */
+  emptyStringAsUndefined?: boolean;
 }
 
 export interface LooseOptions<TShared extends Record<string, ZodType>>
@@ -128,21 +143,6 @@ export interface ServerOptions<
           : never} should not prefixed with ${TPrefix}.`>
       : TServer[TKey];
   }>;
-
-  /**
-   * By default, this library will feed the environment variables directly to
-   * the Zod validator.
-   *
-   * This means that if you have an empty string for a value that is supposed
-   * to be a number (e.g. `PORT=` in a ".env" file), Zod will incorrectly flag
-   * it as a type mismatch violation. Additionally, if you have an empty string
-   * for a value that is supposed to be a string with a default value (e.g.
-   * `DOMAIN=` in an ".env" file), the default value will never be applied.
-   *
-   * In order to solve these issues, we recommend that all new projects
-   * explicitly specify this option as true.
-   */
-  emptyStringAsUndefined?: boolean;
 }
 
 export type ServerClientOptions<