@liquidcommerce/elements-sdk 2.6.0-beta.102 → 2.6.0-beta.103

package/dist/ssr-stub.checkout.esm.js

@@ -1,5 +1,4 @@
 const ELEMENTS_ENV = {
-    DEVELOPMENT: 'development',
     STAGING: 'staging',
     PRODUCTION: 'production',
 };

package/dist/ssr-stub.esm.js

@@ -81,7 +81,6 @@ function isSDKSource(source) {
 }
 
 const ELEMENTS_ENV = {
-    DEVELOPMENT: 'development',
     STAGING: 'staging',
     PRODUCTION: 'production',
 };

package/dist/types/constants/core.constant.d.ts

@@ -1,5 +1,4 @@
 export declare const API_CLIENT_URL: {
-    development: string;
     staging: string;
     production: string;
 };

package/dist/types/enums/core.enum.d.ts

@@ -1,5 +1,4 @@
 export declare const ELEMENTS_ENV: {
-    readonly DEVELOPMENT: "development";
     readonly STAGING: "staging";
     readonly PRODUCTION: "production";
 };

package/docs/v1/api/client.md

@@ -103,7 +103,7 @@ Complete configuration interface for the full SDK.
 ```typescript
 interface ILiquidCommerceElementsConfig {
   // Optional
-  env?: ElementsEnv;  // defaults to 'production' ('development' | 'staging' | 'production')
+  env?: ElementsEnv;  // defaults to 'production' ('staging' | 'production')
   debugMode?: DebugMode;  // 'none' | 'console' | 'panel'
   customTheme?: IClientCustomThemeConfig;
   promoTicker?: IPromoTicker[];
@@ -116,7 +116,7 @@ interface ILiquidCommerceElementsConfig {
 #### Environment
 
 ```typescript
-type ElementsEnv = 'development' | 'staging' | 'production';
+type ElementsEnv = 'staging' | 'production';
 ```
 
 Determines which API environment to use.

package/docs/v1/api/configuration.md

@@ -22,7 +22,7 @@ interface ILiquidCommerceElementsConfig {
 
 | Property | Type | Required | Description |
 |----------|------|----------|-------------|
-| `env` | `'development' \| 'staging' \| 'production'` | No | API environment |
+| `env` | `'staging' \| 'production'` | No | API environment |
 | `promoTicker` | `IPromoTicker[]` | No | Promotional ticker configurations |
 | `customTheme` | `IClientCustomThemeConfig` | No | Theme overrides for all components |
 | `debugMode` | `'none' \| 'console' \| 'panel'` | No | Debug output mode |
@@ -30,7 +30,7 @@ interface ILiquidCommerceElementsConfig {
 | `proxy` | `IElementsProxyConfig` | No | Proxy configuration for API requests |
 | `development` | `ILiquidCommerceElementsDevelopmentConfig` | No | Development/testing options |
 
-> **Note:** `debugMode` (`'console'` or `'panel'`) is **ignored in production** -- it is forced off when `env` is `'production'`. It only takes effect in non-production environments (`'development'` / `'staging'`).
+> **Note:** `debugMode` (`'console'` or `'panel'`) is **ignored in production** -- it is forced off when `env` is `'production'`. It only takes effect outside production (`'staging'`).
 
 ---
 

package/docs/v1/api/typescript-types.md

@@ -310,7 +310,7 @@ See [Actions API](./actions/) for detailed method signatures.
 ### ElementsEnv
 
 ```typescript
-type ElementsEnv = 'development' | 'staging' | 'production';
+type ElementsEnv = 'staging' | 'production';
 ```
 
 ### DebugMode

package/docs/v1/getting-started/concepts.md

@@ -379,7 +379,7 @@ Enable debug mode for detailed logging:
 
 ```javascript
 const client = await Elements('YOUR_API_KEY', {
-  env: 'development',
+  env: 'staging',
   debugMode: 'console'  // or 'panel'
 });
 ```
@@ -409,9 +409,9 @@ Your API key is used for authentication but has limited privileges:
 Use different API keys per environment:
 
 ```javascript
-// Development
-const client = await Elements('dev_key_abc123', {
-  env: 'development'
+// Staging
+const client = await Elements('staging_key_abc123', {
+  env: 'staging'
 });
 
 // Production

package/docs/v1/getting-started/installation.md

@@ -46,7 +46,7 @@ The path segment selects which bundle is served:
 |-----------|----------|-------------|
 | `data-liquid-commerce-elements` | Yes | Identifies this as the Elements SDK script |
 | `data-token` | Yes | Your LiquidCommerce API key |
-| `data-env` | No | Environment: `development`, `staging`, or `production`. Defaults to `production` if omitted. |
+| `data-env` | No | Environment: `staging` or `production`. Defaults to `production` if omitted. |
 | `defer` | Recommended | Allows non-blocking script loading |
 
 ### Where to Place the Script
@@ -264,7 +264,7 @@ The SDK accepts a configuration object during initialization:
 
 ```javascript
 const client = await Elements('YOUR_API_KEY', {
-  env: 'production',           // Optional (defaults to 'production'): 'development' | 'staging' | 'production'
+  env: 'production',           // Optional (defaults to 'production'): 'staging' | 'production'
   debugMode: 'console',         // Optional: 'none' | 'console' | 'panel'
   customTheme: { /* ... */ },   // Optional: Theme customization
   promoTicker: [ /* ... */ ],   // Optional: Promo ticker configuration
@@ -274,7 +274,7 @@ const client = await Elements('YOUR_API_KEY', {
 });
 ```
 
-> **Note:** `debugMode` is ignored when `env` is `'production'`. Debug logging and the debug panel are only activated in non-production environments (`development` or `staging`).
+> **Note:** `debugMode` is ignored when `env` is `'production'`. Debug logging and the debug panel are only activated outside production (`staging`).
 
 See [Configuration Reference](../api/configuration.md) for complete configuration options.
 

package/docs/v1/guides/best-practices.md

@@ -269,20 +269,20 @@ Prevents ad blockers and protects API keys.
 ```javascript
 const apiKey = process.env.NODE_ENV === 'production'
   ? 'prod_key_xyz'
-  : 'dev_key_abc';
+  : 'staging_key_abc';
 
 const client = await Elements(apiKey, {
-  env: process.env.NODE_ENV === 'production' ? 'production' : 'development'
+  env: process.env.NODE_ENV === 'production' ? 'production' : 'staging'
 });
 ```
 
 ## Testing
 
-### Use Development Mode
+### Use Staging With Debug Options
 
 ```javascript
 const client = await Elements('YOUR_API_KEY', {
-  env: 'development',
+  env: 'staging',
   debugMode: 'console',  // or 'panel'
   development: {
     openShadowDom: true  // Makes debugging easier

package/docs/v1/reference/analytics.md

@@ -12,13 +12,12 @@ It coexists with a host site's own GTM — see [Coexisting With Your Own GTM](#c
 
 ## Supported Environments
 
-GTM initialization and every event push are enabled in production and staging. When the SDK is running in development or Builder mode, no container is loaded and no events are sent.
+GTM initialization and every event push are enabled in production and staging. When the SDK is running in Builder mode, no container is loaded and no events are sent.
 
 Events are suppressed when any of the following is true:
 
 - `window` is undefined (server-side rendering).
 - The SDK is running in Builder mode.
-- The environment is `development`.
 
 The environment defaults to `production` when none is provided, so a standard production embed is analytics-enabled out of the box; a staging embed is also analytics-enabled when server GTM config is enabled for the partner.
 

package/docs/v1/reference/telemetry.md

@@ -13,7 +13,7 @@ Telemetry is enabled **only** when both conditions are true:
 
 In every other case it is **disabled** and no events are queued or sent:
 
-- Non-production environments (e.g. staging/development).
+- Non-production environments (i.e. staging).
 - A custom API URL / proxy is configured via `development.customApiUrl`.
 - Internal telemetry errors are only logged to the console in non-production or when debugging is enabled — never sent.
 

package/package.json

@@ -3,7 +3,7 @@
   "description": "LiquidCommerce Elements SDK",
   "license": "UNLICENSED",
   "author": "LiquidCommerce Team",
-  "version": "2.6.0-beta.102",
+  "version": "2.6.0-beta.103",
   "homepage": "https://docs.liquidcommerce.co/elements-sdk",
   "repository": {
     "type": "git",