/* eslint-disable custom-rules/no-process-env */
/**
 * Utility to detect if running in a development environment.
 * Compatible with multiple dev servers (Vite, Webpack, etc.)
 *
 * This function safely checks the NODE_ENV in a way that's compatible
 * with tree-shaking and various build tools.
 */
export declare function isDevelopment(): any;
/**
 * Utility to get the current NODE_ENV value.
 * Compatible with multiple dev servers (Vite, Webpack, etc.)
 */
export declare function getNodeEnv(): string;
/**
 * Whether the translation stack has been turned OFF, read from the app's .env:
 *
 *   REACT_APP_I18N_DISABLED=true
 *
 * Defaults to FALSE - absent, empty or unrecognised means the flag is not set,
 * so i18n stays ON and an app that never touches the variable is unaffected.
 * Only an explicit true/1/on/yes disables the stack.
 *
 * ONE variable, `REACT_APP_` prefixed, for both bundlers. That is this repo's
 * convention (see configService/README.md): the Vite apps set
 * `envPrefix: ['VITE_', 'REACT_APP_']` and keep the historical CRA prefix in
 * their env files, so a VITE_-prefixed alias would be a second spelling nobody
 * uses. It is read off BOTH objects because the two bundlers expose it
 * differently - Vite inlines `import.meta.env`, webpack/CRA inlines
 * `process.env` - and the library ships prebuilt, so it cannot know which one
 * consumes it.
 *
 * Accesses are deliberately STATIC member expressions: that is the form both
 * bundlers' replace step inlines, and a computed key silently yields undefined.
 *
 * NOTE: inlined at BUILD time, so flipping this needs a rebuild, not just a
 * redeploy. That is the right trade for a per-environment kill switch; if you
 * ever need to toggle it at runtime it has to move into ConfigService's
 * loadConfigObject instead.
 */
export declare function isI18nDisabled(): boolean;
//# sourceMappingURL=env.d.ts.map