/**
 * Tier of the services.
 * - `dev`: Development tier, pointing to development services on devext.arcgis.com.
 * - `prod`: Production tier, pointing to production services on www.arcgis.com.
 */
export type ServiceTier = 'prod' | 'dev';
/**
 * Category of custom term:
 * - `topic`: Topic, to understand what this item is about.
 * - `location`: Location or area of coverage, to understand which geographic area is included.
 * - `Year`: Year or Vintage, to understand the how recently the data was collected or updated.
 * - `source`: Source organization/program, to understand where the item’s content originated
 */
export type CustomTermCategory = 'topic' | 'location' | 'vintage-year' | 'source';
/**
 * Represents the status of a custom term in the contribution process.
 *
 * - `staged`: The custom term is in the initial stage and has not yet been submitted.
 * - `submitted`: The custom term has been submitted for review.
 * - `approved`: The custom term has been reviewed and approved.
 * - `rejected`: The custom term has been reviewed and rejected.
 * - `expired`: The custom term has expired and is no longer valid.
 */
export type CustomTermStatus = 'staged' | 'submitted' | 'approved' | 'rejected' | 'expired';
/**
 * The service tier of the application.
 * - `dev`: Development tier, pointing to development services on devext.arcgis.com.
 * - `prod`: Production tier, pointing to production services on www.arcgis.com.
 */
export declare let serviceTier: ServiceTier;
/**
 * Indicates if the environment is Node.js.
 */
export declare const isNodeEnv: boolean;
/**
 * Sets the tier for the services.
 *
 * Why is this needed? Why can't we just use the TIER constant based on the hostname?
 * Because these services can also be used in a node.js environment, where the hostname is not available.
 * That's why we need to set the tier explicitly.
 *
 * @param tier - The tier to set for the services.
 */
export declare const setServiceTier: (tier: ServiceTier) => void;