Skip to content

Version Packages - #4

Merged
azahnen merged 1 commit into
mainfrom
changeset-release/main
Sep 30, 2026
Merged

azahnen merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

Copy link
Copy Markdown

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@xtramaps/layer-control-maplibre@1.1.0

Minor Changes

  • d80e22d: Add @xtramaps/layer-control-maplibre (core) and @xtramaps/layer-control-maplibre-react: the LayerControl component extracted from ogcapi-html, supporting nested groups, radio-groups and merge-groups (including sourceLayer auto-collection). Legend icons are now provided by @xtramaps/legend-symbols-maplibre-react instead of a local copy. Mounted via @vis.gl/react-maplibre's useControl/useMap and composed explicitly as a child of @xtramaps/web-map-maplibre-react's MapLibre component (no dependency between the two packages).

@xtramaps/web-map-cesium@1.1.0

Minor Changes

  • d80e22d: Add @xtramaps/web-map-cesium (core) and @xtramaps/web-map-cesium-react: the Cesium map component migrated from ogcapi-html, onto current @cesium/engine/@cesium/widgets (^26/^16, up from ^2.3.0/^2.2.0). Same viewer construction (background imagery, terrain), 3D Tileset loading (including the vertical-shift correction math), and no LayerControl/legend equivalent - the original never had one for Cesium either.

    Unlike the OpenLayers/MapLibre migrations, the original Cesium component was never a React component - it was a single imperative function called once per page load, with no cleanup, no error handling on its async tileset/style loading, and two previously-dead CSS rules (style.css was never imported). web-map-cesium-react wraps the same logic in a useEffect-driven component and makes three deliberate additions the original didn't have, since a reusable library component can be mounted and unmounted repeatedly (Storybook, demos, consumer apps) unlike a one-shot page script:

    • viewer.destroy() runs on unmount
    • viewer/tileset creation failures are caught and logged instead of failing silently
    • the credit-bar CSS rules are now actually imported and applied

    The component mounts once; prop changes after the initial render aren't reflected, matching the original's single-mount design (Cesium never had a dynamic update path the way OpenLayers/MapLibre's TileMatrixSet switching does).

@xtramaps/web-map-maplibre@1.1.0

Minor Changes

  • d80e22d: Add @xtramaps/web-map-maplibre (core) and @xtramaps/web-map-maplibre-react: the MapLibre map component extracted from ogcapi-html, rebuilt on @vis.gl/react-maplibre and current maplibre-gl (^6) instead of the unmaintained react-maplibre-ui. Includes style/data-layer helpers, hover/click popups, and a CanvasOverlay (formerly CanvasPlugin) for rendering arbitrary React children into the map canvas.

@xtramaps/web-map-openlayers@1.1.0

Minor Changes

  • d80e22d: Add @xtramaps/web-map-openlayers (core) and @xtramaps/web-map-openlayers-react: the OpenLayers map component migrated 1:1 from ogcapi-html, onto current rlayers (3.9.0) and ol (10.8.0) instead of the outdated rlayers@1.1.1/ol@6.9.0. Unlike the MapLibre extraction, this is a pure migration with no new LayerControl/legend equivalent — the original component never had one. The globalThis._map.setCurrentTileMatrixSet global bridge is replaced with a forwardRef/useImperativeHandle-based ref API.

@xtramaps/layer-control-maplibre-react@1.1.0

Minor Changes

  • d80e22d: Add @xtramaps/layer-control-maplibre (core) and @xtramaps/layer-control-maplibre-react: the LayerControl component extracted from ogcapi-html, supporting nested groups, radio-groups and merge-groups (including sourceLayer auto-collection). Legend icons are now provided by @xtramaps/legend-symbols-maplibre-react instead of a local copy. Mounted via @vis.gl/react-maplibre's useControl/useMap and composed explicitly as a child of @xtramaps/web-map-maplibre-react's MapLibre component (no dependency between the two packages).

Patch Changes

  • Updated dependencies [d80e22d]
    • @xtramaps/layer-control-maplibre@1.1.0

@xtramaps/web-map-cesium-react@1.1.0

Minor Changes

  • d80e22d: Add @xtramaps/web-map-cesium (core) and @xtramaps/web-map-cesium-react: the Cesium map component migrated from ogcapi-html, onto current @cesium/engine/@cesium/widgets (^26/^16, up from ^2.3.0/^2.2.0). Same viewer construction (background imagery, terrain), 3D Tileset loading (including the vertical-shift correction math), and no LayerControl/legend equivalent - the original never had one for Cesium either.

    Unlike the OpenLayers/MapLibre migrations, the original Cesium component was never a React component - it was a single imperative function called once per page load, with no cleanup, no error handling on its async tileset/style loading, and two previously-dead CSS rules (style.css was never imported). web-map-cesium-react wraps the same logic in a useEffect-driven component and makes three deliberate additions the original didn't have, since a reusable library component can be mounted and unmounted repeatedly (Storybook, demos, consumer apps) unlike a one-shot page script:

    • viewer.destroy() runs on unmount
    • viewer/tileset creation failures are caught and logged instead of failing silently
    • the credit-bar CSS rules are now actually imported and applied

    The component mounts once; prop changes after the initial render aren't reflected, matching the original's single-mount design (Cesium never had a dynamic update path the way OpenLayers/MapLibre's TileMatrixSet switching does).

Patch Changes

  • Updated dependencies [d80e22d]
    • @xtramaps/web-map-cesium@1.1.0

@xtramaps/web-map-maplibre-react@1.1.0

Minor Changes

  • d80e22d: Add @xtramaps/web-map-maplibre (core) and @xtramaps/web-map-maplibre-react: the MapLibre map component extracted from ogcapi-html, rebuilt on @vis.gl/react-maplibre and current maplibre-gl (^6) instead of the unmaintained react-maplibre-ui. Includes style/data-layer helpers, hover/click popups, and a CanvasOverlay (formerly CanvasPlugin) for rendering arbitrary React children into the map canvas.

Patch Changes

  • Updated dependencies [d80e22d]
    • @xtramaps/web-map-maplibre@1.1.0

@xtramaps/web-map-openlayers-react@1.1.0

Minor Changes

  • d80e22d: Add @xtramaps/web-map-openlayers (core) and @xtramaps/web-map-openlayers-react: the OpenLayers map component migrated 1:1 from ogcapi-html, onto current rlayers (3.9.0) and ol (10.8.0) instead of the outdated rlayers@1.1.1/ol@6.9.0. Unlike the MapLibre extraction, this is a pure migration with no new LayerControl/legend equivalent — the original component never had one. The globalThis._map.setCurrentTileMatrixSet global bridge is replaced with a forwardRef/useImperativeHandle-based ref API.

Patch Changes

  • Updated dependencies [d80e22d]
    • @xtramaps/web-map-openlayers@1.1.0

@azahnen
azahnen merged commit e5240fb into main Sep 30, 2026
1 check passed
@azahnen
azahnen deleted the changeset-release/main branch September 30, 2026 07:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant