@arcgis/map-components 5.2.0-next.61 → 5.2.0-next.62

package/dist/components/arcgis-time-bar/customElement.d.ts

@@ -797,8 +797,8 @@ export abstract class ArcgisTimeBar extends LitElement {
    */
   accessor timeZone: string | undefined;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-time-bar component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-time-bar component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | SceneView | undefined;
   /**
@@ -810,7 +810,7 @@ export abstract class ArcgisTimeBar extends LitElement {
    *
    * @param settings - The `arcgis-time-bar` settings to apply to the component. This should be in the format returned by `getTimeSliderSettingsFromWebDocument`.
    * @example
-   * The following example demonstrates how to use `getTimeSliderSettingsFromWebDocument` and `applyTimeSliderSettings`
+   * The following example demonstrates how to use `getTimeSliderSettingsFromWebDocument` and `applyTimeSettings`
    * together to extract `arcgis-time-bar` settings from a web map and apply them to the `arcgis-time-bar` component.
    * ```html
    * <arcgis-map basemap="satellite" zoom="6" center="-2,54">
@@ -834,11 +834,11 @@ export abstract class ArcgisTimeBar extends LitElement {
    *
    *   const timeBarElement = document.querySelector("arcgis-time-bar");
    *   const timeBar = await timeBarElement.componentOnReady();
-   *   timeBar.applyTimeSliderSettings(timeSliderSettings);
+   *   timeBar.applyTimeSettings(timeSliderSettings);
    * </script>
    * ```
    */
-  applyTimeSliderSettings(settings: Pick<ArcgisTimeBar, "fullTimeExtent" | "loop" | "mode" | "playRate" | "stops" | "timeExtent">): Promise<void>;
+  applyTimeSettings(settings: Pick<ArcgisTimeBar, "fullTimeExtent" | "loop" | "mode" | "playRate" | "stops" | "timeExtent">): Promise<void>;
   /** Permanently destroy the component. */
   destroy(): Promise<void>;
   /**

package/dist/components/arcgis-time-bar/customElement.js

@@ -513,7 +513,7 @@ class St extends ot {
   #t;
   #e;
   #i;
-  async applyTimeSliderSettings(e) {
+  async applyTimeSettings(e) {
     this._viewModel.set(e);
   }
   async destroy() {

package/dist/components/arcgis-time-bar-slider/customElement.js

@@ -1,18 +1,18 @@
 /* COPYRIGHT Esri - https://js.arcgis.com/5.2/LICENSE.txt */
 import { c as u } from "../../chunks/runtime.js";
 import { css as h, html as a } from "lit";
-import o from "@arcgis/core/time/TimeExtent.js";
+import c from "@arcgis/core/time/TimeExtent.js";
 import { LitElement as v, nothing as f, safeClassMap as g } from "@arcgis/lumina";
-import { createRef as c, ref as d } from "lit/directives/ref.js";
+import { createRef as o, ref as d } from "lit/directives/ref.js";
 import { m as w } from "../../chunks/handle.js";
 import { watch as x } from "@arcgis/core/core/reactiveUtils.js";
-const p = h`:host{background-color:var(--calcite-color-surface-2);block-size:var(--calcite-size-fixed-xxxl);color:var(--calcite-color-text-1);display:flex;flex:1 0 auto;font-family:var(--calcite-font-family);font-size:var(--calcite-font-size-sm);inline-size:auto}.root{align-items:center;block-size:100%;display:flex;inline-size:100%}.slider{--labels-container-width: 100%;flex:1 1 auto;min-inline-size:0}.slider--has-ticks{margin-top:calc(var(--calcite-spacing-md) * -1)}.hidden,.max-date,.min-date{flex:0 0 auto}.hidden{inline-size:0}.max-date,.min-date{inline-size:calc(var(--calcite-size-md) * 3.125)}.popover{padding:var(--calcite-spacing-xxs) var(--calcite-spacing-xs) var(--calcite-spacing-xs)}.ticks-container{flex:1;position:relative;width:100%}.major-ticks,.minor-ticks{inset:0;position:absolute}.major-ticks,.minor-ticks{--arcgis-ticks-tick-transform: unset;--arcgis-ticks-tick-width: var(--calcite-size-px)}.minor-ticks{--arcgis-ticks-tick-length: var(--calcite-size-fixed-xxs)}.major-ticks{--arcgis-ticks-font-weight: var(--calcite-font-weight-normal)}.slider.slider--out-of-range{--arcgis-internal-slider-handle-color: var(--calcite-color-status-danger);--arcgis-internal-slider-track-range-background-color: var(--calcite-color-status-danger)}`;
+const p = h`:host{background-color:var(--calcite-color-surface-2);block-size:var(--calcite-size-fixed-xxxl);color:var(--calcite-color-text-1);display:flex;flex:1 0 auto;font-family:var(--calcite-font-family);font-size:var(--calcite-font-size-sm);inline-size:auto}.root{align-items:center;block-size:100%;display:flex;inline-size:100%}slot[name=max],slot[name=min]{display:flex}.slider{--labels-container-width: 100%;flex:1 1 auto;min-inline-size:calc(var(--calcite-spacing-md) * 15)}.slider--has-ticks{margin-top:calc(var(--calcite-spacing-md) * -1)}.hidden,.max-date,.min-date{flex:0 0 auto}.hidden{inline-size:0}.max-date,.min-date{inline-size:calc(var(--calcite-size-md) * 3.125)}.popover{padding:var(--calcite-spacing-xxs) var(--calcite-spacing-xs) var(--calcite-spacing-xs)}.ticks-container{flex:1;position:relative;width:100%}.major-ticks,.minor-ticks{inset:0;position:absolute}.major-ticks,.minor-ticks{--arcgis-ticks-tick-transform: unset;--arcgis-ticks-tick-width: var(--calcite-size-px)}.minor-ticks{--arcgis-ticks-tick-length: var(--calcite-size-fixed-xxs)}.major-ticks{--arcgis-ticks-font-weight: var(--calcite-font-weight-normal)}.slider.slider--out-of-range{--arcgis-internal-slider-handle-color: var(--calcite-color-status-danger);--arcgis-internal-slider-track-range-background-color: var(--calcite-color-status-danger)}`;
 class T extends v {
   constructor() {
     super(...arguments), this.#e = new ResizeObserver(() => {
       const e = this.#r.value?.clientWidth;
       e && (this._sliderWidth = e);
-    }), this.#n = 3, this.#a = c(), this.#r = c(), this._sliderWidth = 100, this.autoDestroyDisabled = !1, this.showMax = !1, this.showMin = !1, this.showTicks = !1, this.showTimeExtentPopover = !1;
+    }), this.#n = 3, this.#a = o(), this.#r = o(), this._sliderWidth = 100, this.autoDestroyDisabled = !1, this.showMax = !1, this.showMin = !1, this.showTicks = !1, this.showTimeExtentPopover = !1;
   }
   static {
     this.properties = { _activeValue: 16, _sliderFillPlacement: 16, _sliderWidth: 16, _timeExtentEpochValues: 16, activeValue: 32, autoDestroyDisabled: 5, showMax: 5, showMin: 5, showTicks: 5, showTimeExtentPopover: 5, viewModel: 0 };
@@ -91,23 +91,23 @@ class T extends v {
     const n = (r.getTime() - s.getTime()) / t;
     return i.tickFormats.find(({ duration: m }) => m > this.#n * n) ?? i.tickFormats.at(-1);
   }
-  #o(e) {
+  #c(e) {
     this._activeValue = e.target.activeValue;
   }
-  #c(e) {
+  #o(e) {
     const { viewModel: t } = this, i = t?.mode;
     i && (t.timeExtent = this.#d(e.target.values, i), this._activeValue = e.target.activeValue);
   }
   #d([e, t], i) {
     switch (i) {
       case "cumulative-from-end":
-        return new o({ start: new Date(e), end: null });
+        return new c({ start: new Date(e), end: null });
       case "cumulative-from-start":
-        return new o({ start: null, end: new Date(e) });
+        return new c({ start: null, end: new Date(e) });
       case "instant":
-        return new o({ start: new Date(e), end: new Date(e) });
+        return new c({ start: new Date(e), end: new Date(e) });
       case "time-window":
-        return new o({ start: new Date(e), end: new Date(t ?? e) });
+        return new c({ start: new Date(e), end: new Date(t ?? e) });
     }
   }
   render() {
@@ -138,7 +138,7 @@ class T extends v {
       slider: !0,
       "slider--has-ticks": this.showTicks,
       "slider--out-of-range": e.isOutOfRange
-    })} .disabled=${!e.interactive} fill-placement=${this._sliderFillPlacement ?? f} .max=${s} .min=${i} @arcgisActiveValueChange=${this.#o} @arcgisInput=${this.#c} precision=0 .steps=${e.effectiveStopsEpoch} .values=${this._timeExtentEpochValues} ${d(this.#r)}>${this.#h()}${this.#g(e, i, s)}</arcgis-slider>`;
+    })} .disabled=${!e.interactive} fill-placement=${this._sliderFillPlacement ?? f} .max=${s} .min=${i} @arcgisActiveValueChange=${this.#c} @arcgisInput=${this.#o} precision=0 .steps=${e.effectiveStopsEpoch} .values=${this._timeExtentEpochValues} ${d(this.#r)}>${this.#h()}${this.#g(e, i, s)}</arcgis-slider>`;
   }
   #g(e, t, i) {
     return this.showTicks ? a`<div slot=content-end class="ticks-container"><arcgis-ticks class="minor-ticks" .max=${i} .min=${t} mode=value .values=${this.#s}></arcgis-ticks><arcgis-ticks class="major-ticks" .labelFormatter=${e.majorTickFormatter} .max=${i} .min=${t} mode=value show-labels .values=${this.#i}></arcgis-ticks></div>` : null;

package/dist/components/arcgis-time-slider/customElement.d.ts

@@ -448,8 +448,8 @@ export abstract class ArcgisTimeSlider extends LitElement {
    */
   accessor timeZone: string;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-time-slider component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-time-slider component will be associated with a map or scene component rather than using the `view` property.
    *
    * @example
    * ```js

package/dist/components/arcgis-time-zone-label/customElement.d.ts

@@ -61,8 +61,8 @@ export abstract class ArcgisTimeZoneLabel extends LitElement {
   /** The state of the component. */
   get state(): State;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-time-zone-label component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-time-zone-label component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | undefined;
   /** Emitted when the value of a property is changed. Use this to listen to changes to properties. */

package/dist/components/arcgis-track/customElement.d.ts

@@ -219,8 +219,8 @@ export abstract class ArcgisTrack extends LitElement {
    */
   get tracking(): boolean;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-track component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-track component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | SceneView | undefined;
   /**

package/dist/components/arcgis-utility-network-associations/customElement.d.ts

@@ -219,8 +219,8 @@ export abstract class ArcgisUtilityNetworkAssociations extends LitElement {
    */
   accessor utilityNetwork: UtilityNetwork | null | undefined;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-associations component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-associations component will be associated with a map or scene component rather than using the `view` property.
    *
    * @since 4.26
    */

package/dist/components/arcgis-utility-network-trace/customElement.d.ts

@@ -205,8 +205,8 @@ export abstract class ArcgisUtilityNetworkTrace extends LitElement {
    */
   get traceResults(): TraceResultExtend[];
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-trace component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-trace component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | null | undefined;
   checkCanTrace(): Promise<void>;

package/dist/components/arcgis-utility-network-trace-analysis/customElement.d.ts

@@ -276,8 +276,8 @@ export abstract class ArcgisUtilityNetworkTraceAnalysis extends LitElement {
    */
   get traceResultFeatures(): Graphic[];
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-trace-analysis component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-trace-analysis component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | null | undefined;
   /** Permanently destroy the component. */

package/dist/components/arcgis-utility-network-trace-inputs/customElement.d.ts

@@ -161,8 +161,8 @@ export abstract class ArcgisUtilityNetworkTraceInputs extends LitElement {
   get traceLocationFlagInfos(): Collection<FlagInfo>;
   get traceLocations(): TraceLocation[];
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-trace-inputs component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-trace-inputs component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | undefined;
   /** Permanently destroy the component. */

package/dist/components/arcgis-utility-network-trace-location/customElement.d.ts

@@ -107,8 +107,8 @@ export abstract class ArcgisUtilityNetworkTraceLocation extends LitElement {
   /** @required */
   accessor utilityNetwork: UtilityNetwork | undefined;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-trace-location component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-trace-location component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | undefined;
   /** Permanently destroy the component. */

package/dist/components/arcgis-utility-network-trace-location-list/customElement.d.ts

@@ -36,8 +36,8 @@ export abstract class ArcgisUtilityNetworkTraceLocationList extends LitElement {
   /** @default "starting-point" */
   accessor traceLocationType: TraceLocationType;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-trace-location-list component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-trace-location-list component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | undefined;
 }

package/dist/components/arcgis-utility-network-trace-results/customElement.d.ts

@@ -159,8 +159,8 @@ export abstract class ArcgisUtilityNetworkTraceResults extends LitElement {
   accessor traceResultFeatures: Graphic[];
   accessor utilityNetwork: UtilityNetwork | undefined;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-trace-results component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-trace-results component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | undefined;
   clearAggregatedGeometryGraphics(): void;

package/dist/components/arcgis-utility-network-validate-topology/customElement.d.ts

@@ -69,8 +69,8 @@ export abstract class ArcgisUtilityNetworkValidateTopology extends LitElement {
    */
   accessor utilityNetwork: UtilityNetwork | null | undefined;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-validate-topology component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-utility-network-validate-topology component will be associated with a map or scene component rather than using the `view` property.
    *
    * @since 4.27
    */

package/dist/components/arcgis-video-player/customElement.d.ts

@@ -250,8 +250,8 @@ export abstract class ArcgisVideoPlayer extends LitElement {
   /** The current state of the component. */
   get state(): "error" | VideoState;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-video-player component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-video-player component will be associated with a map or scene component rather than using the `view` property.
    *
    * @example
    * // Set the video player view model's view to a map view.

package/dist/components/arcgis-volume-measurement/customElement.d.ts

@@ -392,8 +392,8 @@ export abstract class ArcgisVolumeMeasurement extends LitElement {
    */
   get state(): VolumeMeasurementState;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-volume-measurement component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-volume-measurement component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: SceneView | undefined;
   /**

package/dist/components/arcgis-weather/customElement.d.ts

@@ -236,8 +236,8 @@ export abstract class ArcgisWeather extends LitElement {
   /** The current state of the component. */
   get state(): WeatherState;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-weather component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-weather component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: SceneView | undefined;
   /** Permanently destroy the component. */

package/dist/components/arcgis-zoom/customElement.d.ts

@@ -68,8 +68,8 @@ export abstract class ArcgisZoom extends LitElement {
   /** The current state of the component. */
   get state(): State;
   /**
-   * The view associated with the component. 
-   *   > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-zoom component will be associated with a map or scene component rather than using the `view` property.
+   * The view associated with the component.
+   * > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the arcgis-zoom component will be associated with a map or scene component rather than using the `view` property.
    */
   accessor view: MapView | SceneView | undefined;
   /**

package/dist/components/arcgis-zoom/customElement.js

@@ -1,46 +1,22 @@
 /* COPYRIGHT Esri - https://js.arcgis.com/5.2/LICENSE.txt */
-import { c as u } from "../../chunks/runtime.js";
-import { css as m, html as d } from "lit";
-import { when as h } from "@arcgis/core/core/reactiveUtils.js";
-import { LitElement as f, createEvent as i, nothing as r, safeClassMap as y } from "@arcgis/lumina";
-import { usePropertyChange as g } from "@arcgis/lumina/controllers";
-import { u as b } from "../../chunks/useT9n.js";
-import { u as p } from "../../chunks/useView.js";
+import { c } from "../../chunks/runtime.js";
+import { html as l } from "lit";
+import { when as m } from "@arcgis/core/core/reactiveUtils.js";
+import { LitElement as u, createEvent as a, nothing as e, safeClassMap as h } from "@arcgis/lumina";
+import { usePropertyChange as d } from "@arcgis/lumina/controllers";
+import { u as y } from "../../chunks/useT9n.js";
+import { u as g } from "../../chunks/useView.js";
+import { s as p, c as n, a as r } from "../../chunks/zoom.js";
 import { g as z } from "../../chunks/globalCss.js";
-function c(t) {
-  if (!t)
-    return !1;
-  if (t.type === "3d")
-    return t.ready;
-  if (!t?.ready)
-    return !1;
-  const a = l(t), o = t.constraints?.effectiveMaxScale;
-  return o === 0 || a > o;
-}
-function n(t) {
-  if (!t)
-    return !1;
-  if (t.type === "3d")
-    return t.ready;
-  if (!t?.ready)
-    return !1;
-  const a = l(t), o = t.constraints?.effectiveMinScale;
-  return o === 0 || a < o;
-}
-function l(t) {
-  const e = t?.animation?.target;
-  return (e && "then" in e ? void 0 : e?.scale) ?? t?.scale ?? 0;
-}
-const v = m`.arcgis-button{--calcite-icon-color: var(--calcite-color-text-3);--calcite-button-background-color: var(--calcite-color-foreground-1);color:var(--calcite-color-text-3);line-height:var(--calcite-font-line-height-relative-tight);calcite-button{--calcite-offset-invert-focus: 1}display:flex;flex-flow:column;cursor:pointer;background-color:var(--calcite-color-foreground-1);font-size:var(--calcite-font-size);:hover{--calcite-icon-color: var(--calcite-color-text-1);--calcite-button-background-color: var(--calcite-color-transparent-hover)}}:host{display:flex;max-width:fit-content}.zoom-out{border-block-start:solid 1px var(--calcite-color-border-1)}.horizontal{flex-flow:row-reverse nowrap}.horizontal .zoom-out{border-block-start:none;border-inline-end:solid 1px var(--calcite-color-border-1)}`;
-class x extends f {
+class b extends u {
   constructor() {
-    super(...arguments), this.messages = b({}), this._state = "disabled", this.view = p(this), this.autoDestroyDisabled = !1, this.icon = "magnifying-glass-plus", this.layout = "vertical", this.visualScale = "m", this.arcgisActionZoom = i(), this.arcgisPropertyChange = g()("state"), this.arcgisReady = i();
+    super(...arguments), this.messages = y({}), this._state = "disabled", this.view = g(this), this.autoDestroyDisabled = !1, this.icon = "magnifying-glass-plus", this.layout = "vertical", this.visualScale = "m", this.arcgisActionZoom = a(), this.arcgisPropertyChange = d()("state"), this.arcgisReady = a();
   }
   static {
     this.properties = { _state: 16, view: 0, autoDestroyDisabled: 5, icon: 1, label: 1, layout: 3, messageOverrides: 0, referenceElement: 1, visualScale: 1, state: 32 };
   }
   static {
-    this.styles = v;
+    this.styles = p;
   }
   get state() {
     return this._state;
@@ -56,24 +32,24 @@ class x extends f {
   }
   loaded() {
     this.manager.onLifecycle(() => [
-      h(() => this.view?.ready ? "ready" : "disabled", (e) => {
-        this._state = e;
+      m(() => this.view?.ready ? "ready" : "disabled", (o) => {
+        this._state = o;
       }, { sync: !0, initial: !0 })
     ]);
   }
-  async zoomBy(e) {
-    const { view: a } = this, o = e === 1;
-    !(o ? c(a) : n(a)) || !a || (this.arcgisActionZoom.emit({ action: o ? "zoomIn" : "zoomOut" }), o ? await a.zoomIn() : await a.zoomOut());
+  async zoomBy(o) {
+    const { view: t } = this, s = o === 1;
+    !(s ? n(t) : r(t)) || !t || (this.arcgisActionZoom.emit({ action: s ? "zoomIn" : "zoomOut" }), s ? await t.zoomIn() : await t.zoomOut());
   }
   render() {
-    const e = c(this.view), a = n(this.view), { zoomIn: o, zoomOut: s } = this.messages;
-    return d`<div class=${y({
+    const o = n(this.view), t = r(this.view), { zoomIn: s, zoomOut: i } = this.messages;
+    return l`<div class=${h({
       [z.arcgisButton]: !0,
       horizontal: this.layout === "horizontal"
-    })}><calcite-button class="zoom-in" .disabled=${!e} icon-start=plus kind=neutral .label=${o} @click=${this.zoomIn} .scale=${this.visualScale} title=${o ?? r}></calcite-button><calcite-button class="zoom-out" .disabled=${!a} icon-start=minus kind=neutral .label=${s} @click=${this.zoomOut} .scale=${this.visualScale} title=${s ?? r}></calcite-button></div>`;
+    })}><calcite-button class="zoom-in" .disabled=${!o} icon-start=plus kind=neutral .label=${s} @click=${this.zoomIn} .scale=${this.visualScale} title=${s ?? e}></calcite-button><calcite-button class="zoom-out" .disabled=${!t} icon-start=minus kind=neutral .label=${i} @click=${this.zoomOut} .scale=${this.visualScale} title=${i ?? e}></calcite-button></div>`;
   }
 }
-u("arcgis-zoom", x);
+c("arcgis-zoom", b);
 export {
-  x as ArcgisZoom
+  b as ArcgisZoom
 };

package/dist/controllers/useT9n.d.ts

@@ -0,0 +1,3 @@
+import type { UseT9n } from "@arcgis/lumina/controllers";
+
+export const useT9n: UseT9n;