ArcGIS widget-removal survival guide

Every classic ArcGIS JS SDK widget (esri/widgets/* / @arcgis/core/widgets/*) is deprecated as of ArcGIS JS 5.0 and is removed at 6.0 — as early as Q1 2027. If your app constructs any of these widgets, that code stops compiling and running when you take the 6.0 upgrade.

This guide answers, for each deprecated widget, what happens if you migrate to Honua/MapLibre instead of rewriting onto Esri's web components. Dispositions are deliberately honest — including "no equivalent" — in the spirit of docs/migration-punch-list.md.

This document is generated from the versioned disposition data in src/migration/widget-dispositions.ts (v1.4.0); the honua-migrate widget scanner consumes the same data, so the scanner report and this guide cannot drift apart. The deprecated-widget inventory is pinned per ArcGIS release against https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets.html (5.0 deprecation list) and updated manually.

Scan your app first

# Human-readable table (also: --json, --markdown, --gate <pct>, --report <file>)
npm run scan:arcgis:widgets -- ./src

The report inventories every widget usage site (ESM imports, AMD require([...]) arrays, and dynamic $arcgis.import(...) specifiers), joins each row to the disposition below, and emits an overall automated/assisted/manual split against the 6.0 removal deadline. --gate <pct> makes CI fail when the automated share drops below the threshold.

Disposition taxonomy

• Automated (automated): The honua-migrate codemod deterministically rewrites the import and safe constructor call sites to a Honua compat shim from @honua/sdk-esri-compat. Unsafe option literals fall through to an annotated manual TODO.
• Compat shim (compat-shim): A Honua compat shim exists and the codemod rewrites to it, but no native Honua element does the job yet — the shim is the destination, not a waypoint. Treat the migration as assisted and verify app-specific behavior by hand.
• App platform (app-platform): A native Honua app-platform element ships for this capability, and it is the destination for a deliberate rewrite. The codemod still rewrites to the compat shim, so migrating and adopting the element are separate steps — read the row's parity delta for what the element does not cover.
• MapLibre plugin (maplibre-plugin): The capability is served by a MapLibre control or community plugin wired up by hand. (Reserved: no widget currently carries this disposition; several automated rows note the MapLibre-native control underneath.)
• Manual workaround (manual-workaround): No drop-in replacement. The row documents an explicit, honest workaround that is real app work you own.
• No equivalent (no-equivalent): No Honua or MapLibre surface reproduces the widget today. Apps that depend on it need a product decision, not a rewrite.

Readiness buckets: automated counts as automated; compat-shim, app-platform, and maplibre-plugin count as assisted; manual-workaround and no-equivalent count as manual.

A compat-backed row may also list a direct @honua/app-platform component. That component is the recommended destination for a deliberate UI rewrite; the disposition still describes what honua-migrate can automate today.

A shim-backed disposition is about the migration path, not about whether a native component exists. app-platform rows ship one and name it; compat-shim rows do not. Both are rewritten by the codemod to the same shim, so migrating and adopting the native element are separate steps. Read each row's Parity delta for what the native component does not cover — that field is measured against the shipping code, not assumed.

Summary

Widget dispositions

Per-widget details

AreaMeasurement2D

• Disposition: app-platform (App platform)
• Modules: @arcgis/core/widgets/AreaMeasurement2D, esri/widgets/AreaMeasurement2D
• Target: AreaMeasurement2DCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/measurement-2d.ts
• Direct app-platform component: <honua-measurement> from @honua/app-platform/web-components
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites, but the shim covers the core workflow rather than the full ArcGIS surface — plan hands-on verification of app-specific behavior after migration. Rendering is not byte-identical to ArcGIS.
• Parity delta: A native element ships: <honua-measurement> in area mode. Results are formatted metric-only with automatic scaling — m/km for distance, m²/ha/km² for area (formatDistance / formatArea in src/web-components/measurement.ts). ArcGIS's unit and unitOptions, including the whole imperial set (feet, miles, acres, square-miles), have no equivalent, and there is no viewModel for driving measurement state from outside the element. Math itself is at parity: distance and area come from the geodesic length / area ops in @honua/geometry, the same ones behind geometryEngine parity elsewhere in the SDK. The in-progress sketch overlay needs a map exposing addSource / addLayer; on other maps the numbers are still produced, without the overlay.

App-platform usage (the module import auto-registers the element):

import "@honua/app-platform/web-components";

<honua-map id="map"></honua-map>
<honua-measurement for="map"></honua-measurement>

Attribution

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/Attribution, esri/widgets/Attribution
• Target: AttributionCompat from @honua/sdk-esri-compat (MapLibre AttributionControl underneath)
• Compat shim source: src/esri-compat/controls.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

BasemapGallery

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/BasemapGallery, esri/widgets/BasemapGallery
• Target: BasemapGalleryCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/basemap-gallery.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

BasemapLayerList

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/BasemapLayerList, esri/widgets/BasemapLayerList
• Target: BasemapLayerListCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/basemap-layer-list.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

BasemapToggle

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/BasemapToggle, esri/widgets/BasemapToggle
• Target: BasemapToggleCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/controls.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

Bookmarks

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/Bookmarks, esri/widgets/Bookmarks
• Target: BookmarksCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/bookmarks.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

Compass

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/Compass, esri/widgets/Compass
• Target: CompassCompat from @honua/sdk-esri-compat (MapLibre NavigationControl covers the same gesture natively)
• Compat shim source: src/esri-compat/controls.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

CoordinateConversion

• Disposition: compat-shim (Compat shim)
• Modules: @arcgis/core/widgets/CoordinateConversion, esri/widgets/CoordinateConversion
• Target: CoordinateConversionCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/coordinate-conversion.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites, but the shim covers the core workflow rather than the full ArcGIS surface — plan hands-on verification of app-specific behavior after migration. Rendering is not byte-identical to ArcGIS. Custom coordinate formats beyond the built-in set are not reproduced.
• Parity delta: No native element exists — this is one of the three genuinely missing ones. The shim implements exactly three formats (lonlat, dms, dd — CoordinateFormatCompat in src/esri-compat/coordinate-conversion.ts); MGRS, UTM, and USNG are absent, as is ArcGIS's custom ConversionInfo format authoring. Conversion is one-way: setLocation() formats a location, and there is no parse path for typing a coordinate to move the map, so ArcGIS's capture/reverse input mode has no equivalent.

Daylight

• Disposition: no-equivalent (No equivalent)
• Modules: @arcgis/core/widgets/Daylight, esri/widgets/Daylight
• Target: None. Requires a 3D scene with sun/shadow simulation.
• Notes: SceneView/3D analysis widget. Honua's SceneViewCompat is 2D-behavior only and no Honua or MapLibre surface reproduces this widget today (see docs/migration-punch-list.md, parity gap 1). Apps that depend on it need a product decision, not a code rewrite.

Directions

• Disposition: compat-shim (Compat shim)
• Modules: @arcgis/core/widgets/Directions, esri/widgets/Directions
• Target: DirectionsCompat from @honua/sdk-esri-compat backed by HonuaRouteService (RouteTask parity)
• Compat shim source: src/esri-compat/directions.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites, but the shim covers the core workflow rather than the full ArcGIS surface — plan hands-on verification of app-specific behavior after migration. Rendering is not byte-identical to ArcGIS. Only RouteTask-backed routing is shimmed; service-area, closest-facility, and OD-cost-matrix flows remain unsupported (docs/migration-punch-list.md, parity gap 3).
• Parity delta: No native element exists, and building one now would be premature: the delta is a server gap, not a component gap. HonuaRouteService covers RouteTask-equivalent routing; service-area, closest-facility, and OD-cost-matrix have no server surface to bind to until honua-server#2447 (directions + isochrone API) lands. Turn-by-turn maneuver text, route editing by dragging stops, and travel-mode selection all depend on that API's shape.

DistanceMeasurement2D

• Disposition: app-platform (App platform)
• Modules: @arcgis/core/widgets/DistanceMeasurement2D, esri/widgets/DistanceMeasurement2D
• Target: DistanceMeasurement2DCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/measurement-2d.ts
• Direct app-platform component: <honua-measurement> from @honua/app-platform/web-components
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites, but the shim covers the core workflow rather than the full ArcGIS surface — plan hands-on verification of app-specific behavior after migration. Rendering is not byte-identical to ArcGIS.
• Parity delta: A native element ships: <honua-measurement> in distance mode. Results are formatted metric-only with automatic scaling — m/km for distance, m²/ha/km² for area (formatDistance / formatArea in src/web-components/measurement.ts). ArcGIS's unit and unitOptions, including the whole imperial set (feet, miles, acres, square-miles), have no equivalent, and there is no viewModel for driving measurement state from outside the element. Math itself is at parity: distance and area come from the geodesic length / area ops in @honua/geometry, the same ones behind geometryEngine parity elsewhere in the SDK. The in-progress sketch overlay needs a map exposing addSource / addLayer; on other maps the numbers are still produced, without the overlay.

App-platform usage (the module import auto-registers the element):

import "@honua/app-platform/web-components";

<honua-map id="map"></honua-map>
<honua-measurement for="map"></honua-measurement>

Editor

• Disposition: app-platform (App platform)
• Modules: @arcgis/core/widgets/Editor, esri/widgets/Editor
• Target: EditorCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/editor.ts
• Direct app-platform component: <honua-editor> from @honua/app-platform/web-components
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites, but the shim covers the core workflow rather than the full ArcGIS surface — plan hands-on verification of app-specific behavior after migration. Rendering is not byte-identical to ArcGIS. Attribute + geometry editing against feature services works; advanced form elements and utility-network editing do not.
• Parity delta: Two native elements ship: <honua-editor> for the map-bound edit workflow and <honua-feature-editor> for attribute drafts, the latter with undo/redo (Ctrl/Cmd+Z), Escape-to-cancel, a polite live region, and focus/selection that survive re-render so an unrelated realtime change never interrupts typing. The delta is form layout, not editing: grouped and conditional field layouts, Arcade-driven expressions, and utility-network editing are absent. That gap is owned elsewhere by design — honua-server ADR-0069 defines honua.form-package.v1 and honua-server#3244 adopts UI5 for form layout, fields, and validation. Building a bespoke form renderer here would be thrown away.

App-platform usage (the module import auto-registers the element):

import "@honua/app-platform/web-components";

<honua-map id="map"></honua-map>
<honua-editor for="map"></honua-editor>
<!-- richer attribute editing: <honua-feature-editor> from src/web-components/feature-editor.ts -->

ElevationProfile

• Disposition: manual-workaround (Manual workaround)
• Modules: @arcgis/core/widgets/ElevationProfile, esri/widgets/ElevationProfile
• Target: No drop-in widget. Sample the profile geometry yourself (e.g. @honua/sdk-js/geometry densify + an elevation/terrain source such as maplibre-gl queryTerrainElevation) and chart with your own charting library.
• Notes: There is no ElevationProfile shim and no automated rewrite. The workaround is honest but real work: profile sampling, unit handling, and chart UX are app code you own after migration.
• Parity delta: No native element and no shim — the only 2D row in the inventory with neither (the five no-equivalent rows — Daylight, LineOfSight, ShadowCast, Slice, Weather — have neither either, but each needs a 3D scene before a component question even arises), and one of the three genuinely missing components. Every piece it needs already exists separately: densification in @honua/sdk-js/geometry, terrain sampling via queryTerrainElevation, and charting via <honua-chart>. What is missing is the component that composes them, plus the elevation-source binding contract that says where the terrain comes from. ArcGIS's multi-profile comparison (ground vs input line vs view) and hover-to-locate-on-map are additional surface beyond a first cut.

Expand

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/Expand, esri/widgets/Expand
• Target: ExpandCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/expand.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

Feature

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/Feature, esri/widgets/Feature
• Target: FeatureCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/feature.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

FeatureForm

• Disposition: compat-shim (Compat shim)
• Modules: @arcgis/core/widgets/FeatureForm, esri/widgets/FeatureForm
• Target: FeatureFormCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/feature-form.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites, but the shim covers the core workflow rather than the full ArcGIS surface — plan hands-on verification of app-specific behavior after migration. Rendering is not byte-identical to ArcGIS. Arcade-driven form expressions are not evaluated.
• Parity delta: No native element exists, and none should be built in this repo. A standalone form component would be superseded by the form-package work: honua-server ADR-0069 owns the honua.form-package.v1 contract and honua-server#3244 owns the UI5 field/validation layer. The remaining shim-level gap is Arcade expression evaluation, which is a language runtime rather than a component.

FeatureTable

• Disposition: app-platform (App platform)
• Modules: @arcgis/core/widgets/FeatureTable, esri/widgets/FeatureTable
• Target: FeatureTableCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/feature-table.ts
• Direct app-platform component: <honua-feature-table> from @honua/app-platform/web-components
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites, but the shim covers the core workflow rather than the full ArcGIS surface — plan hands-on verification of app-specific behavior after migration. Rendering is not byte-identical to ArcGIS. Related-records and popup interaction flows are exercised by the demo fixtures; column virtualization and attachment editing differ from ArcGIS.
• Parity delta: A native element ships: <honua-feature-table>. Its bounded lane already does the parts usually assumed missing — a virtualized window, remote paging driven by real scroll geometry, multi-column sort from header clicks, total-known/estimated/partial/stale/cancelled truth, and realtime reconciliation conflicts announced in a polite live region — over a full WAI-ARIA grid keyboard contract (arrows, Home/End, PageUp/PageDown, roving tabindex). The notes line above predates that work and is stale on virtualization. Remaining ArcGIS gaps: attachment editing, related-records as a first-class panel, and grid chrome (column menus, field formatting UI), the last of which is data-grid furniture owned by honua-server#3244 (UI5).

App-platform usage (the module import auto-registers the element):

import "@honua/app-platform/web-components";

<honua-map id="map"></honua-map>
<honua-feature-table for="map"></honua-feature-table>
<!-- bounded lane: element.table = createHonuaFeatureTable({ ... }) -->

FeatureTemplates

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/FeatureTemplates, esri/widgets/FeatureTemplates
• Target: FeatureTemplatesCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/feature-templates.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

Fullscreen

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/Fullscreen, esri/widgets/Fullscreen
• Target: FullscreenCompat from @honua/sdk-esri-compat (MapLibre FullscreenControl underneath)
• Compat shim source: src/esri-compat/controls.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

Home

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/Home, esri/widgets/Home
• Target: HomeCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/controls.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

LayerList

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/LayerList, esri/widgets/LayerList
• Target: LayerListCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/layer-list.ts
• Direct app-platform component: <honua-layer-list> from @honua/app-platform/web-components
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

App-platform usage (the module import auto-registers the element):

import "@honua/app-platform/web-components";

<honua-map id="map"></honua-map>
<honua-layer-list for="map"></honua-layer-list>

Legend

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/Legend, esri/widgets/Legend
• Target: LegendCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/legend.ts
• Direct app-platform component: <honua-legend> from @honua/app-platform/web-components
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

App-platform usage (the module import auto-registers the element):

import "@honua/app-platform/web-components";

<honua-map id="map"></honua-map>
<honua-legend for="map"></honua-legend>

LineOfSight

• Disposition: no-equivalent (No equivalent)
• Modules: @arcgis/core/widgets/LineOfSight, esri/widgets/LineOfSight
• Target: None. Requires 3D scene geometry intersection analysis.
• Notes: SceneView/3D analysis widget. Honua's SceneViewCompat is 2D-behavior only and no Honua or MapLibre surface reproduces this widget today (see docs/migration-punch-list.md, parity gap 1). Apps that depend on it need a product decision, not a code rewrite.

Locate

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/Locate, esri/widgets/Locate
• Target: LocateCompat from @honua/sdk-esri-compat (MapLibre GeolocateControl covers the same behavior natively)
• Compat shim source: src/esri-compat/controls.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

Measurement

• Disposition: app-platform (App platform)
• Modules: @arcgis/core/widgets/Measurement, esri/widgets/Measurement
• Target: MeasurementCompat from @honua/sdk-esri-compat (2D distance/area only)
• Compat shim source: src/esri-compat/measurement.ts
• Direct app-platform component: <honua-measurement> from @honua/app-platform/web-components
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites, but the shim covers the core workflow rather than the full ArcGIS surface — plan hands-on verification of app-specific behavior after migration. Rendering is not byte-identical to ArcGIS. 3D measurement modes are not supported.
• Parity delta: A native element ships: <honua-measurement>, and Measurement, AreaMeasurement2D, and DistanceMeasurement2D collapse into it rather than into three components. Modes are off | distance | area only (HonuaMeasureMode); ArcGIS's 3D direct-line mode has no equivalent and needs a scene, not a component. Results are formatted metric-only with automatic scaling — m/km for distance, m²/ha/km² for area (formatDistance / formatArea in src/web-components/measurement.ts). ArcGIS's unit and unitOptions, including the whole imperial set (feet, miles, acres, square-miles), have no equivalent, and there is no viewModel for driving measurement state from outside the element. Math itself is at parity: distance and area come from the geodesic length / area ops in @honua/geometry, the same ones behind geometryEngine parity elsewhere in the SDK. The in-progress sketch overlay needs a map exposing addSource / addLayer; on other maps the numbers are still produced, without the overlay.

App-platform usage (the module import auto-registers the element):

import "@honua/app-platform/web-components";

<honua-map id="map"></honua-map>
<honua-measurement for="map"></honua-measurement>

Popup

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/Popup, esri/widgets/Popup
• Target: PopupCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/popup.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS. Popup actions and fieldInfos format callbacks migrate for the simple case only (docs/migration-punch-list.md, parity gap 5).

Print

• Disposition: app-platform (App platform)
• Modules: @arcgis/core/widgets/Print, esri/widgets/Print
• Target: PrintCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/print.ts
• Direct app-platform component: <honua-print-export> from @honua/app-platform/web-components
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites, but the shim covers the core workflow rather than the full ArcGIS surface — plan hands-on verification of app-specific behavior after migration. Rendering is not byte-identical to ArcGIS. Export goes through the Honua rendering pipeline, not an ArcGIS print service; custom print templates need re-authoring.
• Parity delta: A native element ships: <honua-print-export>, covering browser print, snapshot, and sanitized state export. The delta is deliberate rather than unfinished: the SDK bundles no renderer, PDF writer, or image encoder, so snapshot and state export require an application-supplied HonuaExportAdapter and fail closed without one — disabled buttons and an unsupported result carrying HonuaCapabilityNotSupportedError, never a blank image or a partially-credentialed JSON document (src/web-components/export.ts). Browser print works with no adapter but reproduces the on-screen layout only. ArcGIS's print-service layout templates, explicit scale/DPI selection, and author/title/copyright metadata have no equivalent; custom templates need re-authoring against the adapter.

App-platform usage (the module import auto-registers the element):

import "@honua/app-platform/web-components";

<honua-map id="map"></honua-map>
<honua-print-export for="map"></honua-print-export>
<!-- element.exportAdapter = yourAdapter — snapshot/state fail closed without one -->

ScaleBar

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/ScaleBar, esri/widgets/ScaleBar
• Target: ScaleBarCompat from @honua/sdk-esri-compat (MapLibre ScaleControl underneath)
• Compat shim source: src/esri-compat/controls.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

Search

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/Search, esri/widgets/Search
• Target: SearchCompat from @honua/sdk-esri-compat, with LocatorSearchSourceCompat as the address backend
• Compat shim source: src/esri-compat/search.ts
• Direct app-platform component: <honua-search> from @honua/app-platform/web-components
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS. Layer search works out of the box. Address search wires LocatorCompat.toSearchSource() (or LocatorSearchSourceCompat) into sources; the geocoding provider is bring-your-own, so the codemod rewrites the constructor but cannot choose the endpoint. Providers that do not declare suggest (Nominatim) omit the typeahead hook rather than faking it.

App-platform usage (the module import auto-registers the element):

import "@honua/app-platform/web-components";

<honua-map id="map"></honua-map>
<honua-search for="map" source="incidents"></honua-search>

ShadowCast

• Disposition: no-equivalent (No equivalent)
• Modules: @arcgis/core/widgets/ShadowCast, esri/widgets/ShadowCast
• Target: None. Requires a 3D scene with shadow accumulation.
• Notes: SceneView/3D analysis widget. Honua's SceneViewCompat is 2D-behavior only and no Honua or MapLibre surface reproduces this widget today (see docs/migration-punch-list.md, parity gap 1). Apps that depend on it need a product decision, not a code rewrite.

Sketch

• Disposition: app-platform (App platform)
• Modules: @arcgis/core/widgets/Sketch, esri/widgets/Sketch
• Target: SketchCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/sketch.ts
• Direct app-platform component: <honua-sketch-control> from @honua/app-platform/web-components
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites, but the shim covers the core workflow rather than the full ArcGIS surface — plan hands-on verification of app-specific behavior after migration. Rendering is not byte-identical to ArcGIS. Snapping and 3D sketch tools are not reproduced.
• Parity delta: A native element ships: <honua-sketch-control>, with point/line/polygon modes, plus the terra-draw integration and the edit-sketch contracts in src/contract/edit-sketch.ts. Two named gaps remain, both real: snapping (ArcGIS SnappingOptions, self- and feature-snapping) is absent, and 3D sketch tools need a scene. One behaviour reads as a gap but is a decision: the modes render disabled unless the controller has a sketchGeometry provider configured, because the SDK does not bundle a drawing backend.

App-platform usage (the module import auto-registers the element):

import "@honua/app-platform/web-components";

<honua-map id="map"></honua-map>
<honua-sketch-control for="map"></honua-sketch-control>
<!-- requires a sketchGeometry provider on the controller -->

Slice

• Disposition: no-equivalent (No equivalent)
• Modules: @arcgis/core/widgets/Slice, esri/widgets/Slice
• Target: None. Requires 3D scene slicing.
• Notes: SceneView/3D analysis widget. Honua's SceneViewCompat is 2D-behavior only and no Honua or MapLibre surface reproduces this widget today (see docs/migration-punch-list.md, parity gap 1). Apps that depend on it need a product decision, not a code rewrite.

Swipe

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/Swipe, esri/widgets/Swipe
• Target: SwipeCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/swipe.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

TableList

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/TableList, esri/widgets/TableList
• Target: TableListCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/table-list.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

TimeSlider

• Disposition: app-platform (App platform)
• Modules: @arcgis/core/widgets/TimeSlider, esri/widgets/TimeSlider
• Target: TimeSliderCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/time-slider.ts
• Direct app-platform component: <honua-time-slider> from @honua/app-platform/web-components
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites, but the shim covers the core workflow rather than the full ArcGIS surface — plan hands-on verification of app-specific behavior after migration. Rendering is not byte-identical to ArcGIS. Time-aware layer filtering works; stops derived from server time-info metadata should be verified per service. With a container and a registered widget kit the shim now renders through <honua-time-slider>; without the kit it stays state-model-only, and the element's own transport drives the app-platform temporal playback controller rather than the shim's stop list.
• Parity delta: A native element ships: <honua-time-slider>, following the WAI-ARIA slider pattern with full keyboard operation (arrows step, PageUp/PageDown move ten, Home/End jump, RTL-mirrored) and a CSP-safe shadow tree built once so an active drag is never torn out from under the pointer. The delta is in configuration surface, not behaviour: the element observes only label, unavailable-reason, and speeds, and takes everything else from the playback controller (createTemporalPlayback). ArcGIS's declarative stops modes (count / interval / dates), timeVisible, loop, and playRate therefore have no attribute equivalents — they are controller configuration. Stops derived from server time-info metadata should be verified per service.

App-platform usage (the module import auto-registers the element):

import "@honua/app-platform/web-components";

<honua-map id="map"></honua-map>
<honua-time-slider id="time" label="Time"></honua-time-slider>
<!-- element.playback = createTemporalPlayback({ ... }) from @honua/sdk-js/map -->

Track

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/Track, esri/widgets/Track
• Target: TrackCompat from @honua/sdk-esri-compat
• Compat shim source: src/esri-compat/track.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

Weather

• Disposition: no-equivalent (No equivalent)
• Modules: @arcgis/core/widgets/Weather, esri/widgets/Weather
• Target: None. Requires a 3D scene atmosphere/weather renderer.
• Notes: SceneView/3D analysis widget. Honua's SceneViewCompat is 2D-behavior only and no Honua or MapLibre surface reproduces this widget today (see docs/migration-punch-list.md, parity gap 1). Apps that depend on it need a product decision, not a code rewrite.

Zoom

• Disposition: automated (Automated)
• Modules: @arcgis/core/widgets/Zoom, esri/widgets/Zoom
• Target: ZoomCompat from @honua/sdk-esri-compat (MapLibre NavigationControl underneath)
• Compat shim source: src/esri-compat/controls.ts
• Notes: The honua-migrate codemod rewrites the import and safe constructor call sites deterministically; unsafe option literals fall through to an annotated manual TODO. Rendering goes through the Honua widget host, so CSS selectors and DOM structure are not byte-identical to ArcGIS.

Out of scope

These surfaces are intentionally not covered by the dispositions above:

• SceneView / 3D rendering. Honua's SceneViewCompat shares 2D MapView behavior; WebGL/CesiumJS scene parity (environment, global viewing mode, scene layers, camera) is not implemented (punch list, parity gaps 1-2). The 3D analysis widgets above are therefore no-equivalent rather than shimmed.
• Geocoding endpoints. Locator itself is shimmed — LocatorCompat maps addressToLocations, addressesToLocations, locationToAddress, and suggestLocations onto the provider-pluggable geocoding contract, and LocatorSearchSourceCompat is the Search widget's address backend. What is out of scope is the endpoint: providers are bring-your-own (Nominatim / Photon / Pelias / a Honua GeocodeServer), the codemod cannot pick one for you, and a provider that does not declare suggest makes typeahead throw HonuaCapabilityNotSupportedError rather than silently degrading to a forward geocode.
• Geoprocessor / NetworkAnalyst beyond RouteTask. Service-area, closest-facility, OD-cost-matrix, and general geoprocessing have no Honua equivalent yet; the scanner's advanced-widget-or-networking-detected flag calls these out separately (punch list, parity gap 3).

Related reading

• Migration punch list — the honest parity/codemod accounting.
• Third-party OSS ArcGIS app readiness — what the scanner and codemod actually do to real, pinned, third-party open-source ArcGIS apps (including the ones they cannot see at all).
• Honua ⇄ MapLibre migration notes — the honua-maplibre codemod target.
• SDK guide: Migration CLI — every honua-migrate subcommand.