@tileflow/react 0.1.0-alpha.19 → 0.1.0-alpha.20

package/GENERATED_OUTPUT_LICENSE.md

@@ -0,0 +1,21 @@
+# Tileflow generated-output grant
+
+In addition to the rights granted by the Apache License, Version 2.0, Tileflow.dev contributors
+grant recipients a perpetual, worldwide, non-exclusive, no-charge, royalty-free right to use,
+reproduce, modify, display, perform, distribute, sublicense, and commercialize the Tileflow-owned
+parts of output generated by this SDK.
+
+Covered output includes compiled map styles, manifests, receipts, sprites, glyph artifacts, static
+render descriptions, and other build artifacts produced from Tileflow maps or application maps.
+Original Tileflow map definitions, icons, and patterns distributed by `@tileflow/maps` may likewise
+be used, modified, embedded, deployed, and redistributed as part of personal or commercial maps and
+applications.
+
+This grant does not relicense third-party software, fonts, icons, map data, datasets, imagery, or
+other input material. Their licenses, attribution requirements, notices, and use restrictions
+continue to apply to the relevant source and generated output. You are responsible for having the
+rights necessary to process and distribute your own inputs.
+
+This grant does not provide access to Tileflow hosted services or grant rights in Tileflow names,
+logos, or marks. The SDK and generated output are provided without warranties or conditions beyond
+those required by applicable law.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,9 @@
+Tileflow SDK
+Copyright 2026 Tileflow.dev contributors
+
+This product includes software and original map artwork developed by Tileflow.dev contributors.
+
+Third-party materials distributed with a package remain subject to their own license and notice
+files. See THIRD_PARTY_NOTICES.md and asset-adjacent license files where present.
+
+The Tileflow names and marks are not licensed under the Apache License 2.0. See TRADEMARKS.md.

package/README.md

@@ -11,7 +11,8 @@ import 'maplibre-gl/dist/maplibre-gl.css';
 export function App() {
   return (
     <Map
-      map="madrid"
+      source={{kind: 'tileflow', map: 'madrid'}}
+      theme="system"
       center={[-3.7038, 40.4168]}
       zoom={12}
       mapOptions={{
@@ -23,37 +24,200 @@ export function App() {
 }
 ```
 
+## Annotations, tooltips, and popups
+
+Use `annotations` for small application-owned marker sets. Annotation data is serializable, while
+`renderMarker`, `renderTooltip`, and `renderPopup` render native React UI through portals into the
+MapLibre-owned marker and overlay hosts.
+
+```tsx
+import {Map} from '@tileflow/react';
+import {useState} from 'react';
+import type {TileflowAnnotation, TileflowInteractionState} from '@tileflow/interactions';
+
+type Property = {
+  price: number;
+  title: string;
+};
+
+const annotations = [
+  {
+    ariaLabel: 'Apartment in Madrid',
+    coordinate: [-3.7038, 40.4168],
+    data: {price: 320_000, title: 'Apartment in Madrid'},
+    id: 'property-42',
+    kind: 'marker',
+    marker: {content: {kind: 'field', field: 'price'}},
+    tooltip: {content: {kind: 'field', field: 'title'}},
+    popup: {content: {kind: 'view', name: 'property-card'}},
+  },
+] satisfies readonly TileflowAnnotation<Property>[];
+
+export function PropertyMap() {
+  const [interactionState, setInteractionState] = useState<TileflowInteractionState>({popup: null});
+
+  return (
+    <Map
+      source={{kind: 'tileflow', map: 'madrid'}}
+      annotations={annotations}
+      interactionState={interactionState}
+      onInteractionStateChange={setInteractionState}
+      onInteractionDiagnostic={(diagnostic) => console.error(diagnostic)}
+      onInteractionEvent={(event) => console.log(event.type, event.target)}
+      renderMarker={({annotation}) => <strong>EUR {annotation.data.price.toLocaleString()}</strong>}
+      renderPopup={({annotation, close}) => (
+        <article>
+          <h2>{annotation.data.title}</h2>
+          <p>EUR {annotation.data.price.toLocaleString()}</p>
+          <button type="button" onClick={close}>
+            Close
+          </button>
+        </article>
+      )}
+    />
+  );
+}
+```
+
+Omit `interactionState` and use `defaultInteractionState` for uncontrolled popup state. Callback and
+renderer identity changes, annotation updates, and popup state changes do not recreate the MapLibre
+map. Updating an annotation with the same ID preserves its compatible Marker instance and portal
+host.
+
+`renderMarker` is always annotation-only. Without `interactions`, `renderTooltip` and `renderPopup`
+also infer the annotation-specific context, including typed `annotation.data`. When `interactions`
+is present, they receive the common `TileflowInteractionViewContext`; narrow `context.target.kind`
+(or check `annotation in context`) when one renderer serves both annotation and semantic targets.
+
+## Semantic POI interactions
+
+Use `interactions` to attach tooltip or popup behavior to POIs already rendered by a finalized
+Tileflow style. Application code names the `poi` domain, never compiler-generated MapLibre layer
+IDs. The runtime queries only manifest-declared layers and mounts DOM only for the active overlay.
+
+```tsx
+import {Map} from '@tileflow/react';
+import type {TileflowInteractionBinding} from '@tileflow/interactions';
+
+const interactions = [
+  {
+    id: 'poi-details',
+    target: {kind: 'semantic-feature', domain: 'poi', categories: ['food-drink', 'retail']},
+    tooltip: {content: {kind: 'field', field: 'name', fallback: 'Point of interest'}},
+    popup: {content: {kind: 'view', name: 'poi-card'}},
+  },
+] satisfies readonly TileflowInteractionBinding[];
+
+export function PoiMap() {
+  return (
+    <Map
+      source={{kind: 'tileflow', map: 'madrid'}}
+      interactions={interactions}
+      renderPopup={(context) =>
+        context.target.kind === 'semantic-feature' ? (
+          <article>
+            <h2>{String(context.target.feature.properties.name ?? 'Point of interest')}</h2>
+            <button type="button" onClick={context.close}>
+              Close
+            </button>
+          </article>
+        ) : null
+      }
+    />
+  );
+}
+```
+
+Bindings and popup state are validated before reconciliation. An invalid replacement leaves the
+last valid runtime state active and reports structured diagnostics. `interactionState` and
+`defaultInteractionState` are mutually exclusive. Annotation and semantic overlays share one popup
+state, so replacing either target closes the previous popup before opening the next.
+
+`MapProps` also rejects `annotations` together with legacy `markers`, and rejects controlled and
+default interaction state together. Its `mode="image"` branch excludes annotations, markers,
+semantic bindings, interaction state, renderers, and interaction callbacks. JavaScript callers and
+widened inputs still receive the corresponding runtime diagnostics.
+
+`onInteractionDiagnostic` receives each newly reported structured runtime diagnostic. Changing any
+callback identity does not resubscribe the runtime or recreate MapLibre.
+
+Custom portal targets move capture readiness to `loading` until React commits the target and two
+current animation frames complete. Removing or replacing a target invalidates pending frames.
+
+When no render prop is present, text and safe field descriptors use the shared unbranded DOM
+defaults. A `view` descriptor is a dispatch name for an application renderer; it is not HTML or a
+serialized component tree. Tooltip content remains non-interactive, while popup content may contain
+normal React controls.
+
+The legacy `markers` prop remains available during the alpha migration and is normalized through the
+same keyed runtime. Its `label` keeps the existing marker `title`; do not pass `markers` and
+`annotations` together. `mode="image"` cannot render interaction configuration and shows an
+explicit `UNSUPPORTED_MODE` diagnostic without loading MapLibre.
+
 `mapOptions` accepts native MapLibre options except `container` and `style`, which
-Tileflow resolves from the map name, manifest, or explicit style props. Direct
+Tileflow resolves from `source`. Direct
 Tileflow props such as `center`, `zoom`, and `interactive` take priority when
-provided.
+provided. Camera resolution is the same in interactive and image modes: direct props, then
+`mapOptions`, then the published manifest view, then Tileflow's shared runtime defaults.
+
+Every map has exactly one discriminated `source`. Use `kind: 'tileflow'` for a map published in a
+Tileflow manifest. `kind: 'maplibre'` is the unmanaged MapLibre escape hatch for one direct style
+object or URL: it deliberately has no Tileflow theme identity, `system` selection, switching, or
+manifest traceability. Browser components do not compile `tileflow.config.ts`.
+
+Without `manifestUrl`, the exact default is `/tileflow/manifest.json`. If Vite, Webpack, Next, a
+reverse proxy, or the Tileflow plugin publishes it anywhere else, set the final public URL
+explicitly; the component does not attempt runtime base-path discovery. Manifest 404s, unknown map
+IDs, unresolved styles, and unresolved image URLs enter `data-tileflow-state="error"`.
+
+`theme` selects a published theme name. Omitting it uses the map's `defaultTheme`; `"system"` is
+available only when the map declares explicit light and dark mappings. Changes preload fonts, diff
+the style on the existing MapLibre instance, preserve camera and interactions, and roll back if the
+new style fails. `onThemeChange` reports preloading, applying, ready, and error transitions.
 
 To reuse one published map across multiple repos, point every app at the same
 manifest:
 
 ```tsx
-<Map map="madrid" manifestUrl="https://cdn.example.com/tileflow/manifest.json" />
+<Map
+  source={{
+    kind: 'tileflow',
+    map: 'madrid',
+    manifestUrl: 'https://cdn.example.com/tileflow/manifest.json',
+  }}
+/>
 ```
 
-Or bypass the manifest and load a hosted style directly:
+Or deliberately leave the Tileflow theme contract and load one concrete Style JSON directly:
 
 ```tsx
-<Map styleUrl="https://api.tileflow.dev/maps/map_1234567890abcdef/style.json" />
+<Map
+  source={{
+    kind: 'maplibre',
+    style: 'https://cdn.example.com/tileflow/styles/madrid/dark.json',
+  }}
+/>
 ```
 
-For simple hosted static images, use image mode:
+For a lightweight display of an already hosted static image, use image mode:
 
 ```tsx
-<Map map="madrid" mode="image" center={[-3.7038, 40.4168]} zoom={12} />
+<Map
+  source={{kind: 'tileflow', map: 'madrid'}}
+  mode="image"
+  center={[-3.7038, 40.4168]}
+  zoom={12}
+/>
 ```
 
-When `mode="image"` does not include an explicit `imageUrl`, local development
-hosts render the interactive map while `preferLocalDev` is enabled. Production
-hosts render the deployed static image. Set `preferLocalDev={false}` to preview
-the production image behavior locally.
+`Map mode="image"` only resolves an existing image URL (explicitly or from the published map
+manifest) and renders an `<img>`; it does not submit a render scene, create an operation, poll, or
+apply `StaticMap` overlays. This path does not load or evaluate MapLibre. Without an explicit
+`imageUrl`, all environments use the image URL published for the Tileflow source.
 
-For full static scenes with bounds, overlays, and server-side precache, use
-`StaticMap` from `@tileflow/react/static` or helpers from `@tileflow/static`.
+For a new, fully specified render with exact size, center/bounds camera, overlays, idempotency, and
+asynchronous create/poll behavior, use `StaticMap` from `@tileflow/react/static` or helpers from
+`@tileflow/static`.
 
 ```tsx
 import {StaticMap} from '@tileflow/react/static';
@@ -83,13 +247,16 @@ consumer aborts its in-flight request.
 Hosted interactive maps automatically preflight a short-lived commercial session grant before
 eligible resources. Setting `analytics={{enabled: false}}` disables the optional beacon only; it
 does not remove hosted authorization or override a user `mapOptions.transformRequest` callback.
+Direct Tileflow World maps keep early `GRACE` silent, show a compact accessible owner-action pill
+when late `GRACE` is activated, and show a stronger banner in `CLAIM_REQUIRED`. Missing tiles and
+MapLibre failures do not remove that recovery path.
 
 ## Headless capture readiness
 
 Use `captureId` to disambiguate multiple maps with the same configured name:
 
 ```tsx
-<Map map="madrid" captureId="checkout-map" />
+<Map source={{kind: 'tileflow', map: 'madrid'}} captureId="checkout-map" />
 ```
 
 The root element exposes `data-tileflow-map`, optional `data-tileflow-capture-id`, and
@@ -98,4 +265,11 @@ and two animation frames; style/data work returns it to loading. Image mode wait
 successful load fallback, including cached hydration. `tileflow capture` uses these markers for
 application scenes and requires exactly one target.
 
+## Compatibility
+
+The supported peer window is React 18-19 and MapLibre GL JS 5-6. Compatibility smoke tests install
+the exact lower bound and the first release of every accepted major from packed Tileflow tarballs,
+typecheck a consumer, and render the image/SSR path while rejecting any MapLibre import. Future
+majors stay outside the peer range until that matrix passes.
+
 Docs: https://tileflow.dev/docs

package/TRADEMARKS.md

@@ -0,0 +1,10 @@
+# Tileflow trademarks
+
+The Apache License, Version 2.0, and the Tileflow generated-output grant do not grant permission to
+use the Tileflow name, `tileflow.dev`, logos, service marks, product names, or other Tileflow brand
+features except for reasonable and customary use that truthfully describes the origin of the SDK or
+compatibility with Tileflow, and for reproducing required notices.
+
+You may not use Tileflow brand features in a way that suggests sponsorship, endorsement, or an
+official Tileflow product when none exists. Third-party names and marks remain the property of their
+respective owners.

package/dist/index.d.ts

@@ -1,22 +1,23 @@
 import * as react from 'react';
-import { CSSProperties, ImgHTMLAttributes } from 'react';
+import { CSSProperties, ImgHTMLAttributes, ReactNode } from 'react';
 import { MapOptions, Map as Map$1 } from 'maplibre-gl';
-import { TileflowConfig, MapLibreStyle, TileflowProjectThemes, TileflowMapMarker, TileflowAnalytics } from '@tileflow/core';
+import { TileflowThemeTransition } from '@tileflow/core/browser';
+import { TileflowRuntimeSource, TileflowThemeSelection, TileflowAnalytics, TileflowMapMarker } from '@tileflow/core/runtime';
+import { TileflowAnnotation, TileflowInteractionState, TileflowAnnotationViewContext, TileflowInteractionBinding, TileflowInteractionViewContext, TileflowInteractionDiagnostic, TileflowInteractionEvent } from '@tileflow/interactions';
+
+type TileflowMapStyleSourceProps = {
+    source: TileflowRuntimeSource;
+    theme?: TileflowThemeSelection;
+};
 
 type MapMarker = TileflowMapMarker;
+type TileflowMapSource = TileflowRuntimeSource;
 type TileflowMapOptions = Omit<MapOptions, 'container' | 'style'>;
-type MapProps = {
+type TileflowAnnotationRenderer<TAnnotation extends TileflowAnnotation = TileflowAnnotation> = (context: TileflowAnnotationViewContext<TAnnotation>) => ReactNode;
+type TileflowInteractionRenderer<TAnnotation extends TileflowAnnotation = TileflowAnnotation> = (context: TileflowInteractionViewContext<TAnnotation>) => ReactNode;
+type MapSharedProps = {
     captureId?: string;
-    map?: string;
-    mode?: 'interactive' | 'image';
-    config?: TileflowConfig;
-    style?: MapLibreStyle;
-    styleUrl?: string;
     imageUrl?: string;
-    styleBaseUrl?: string;
-    themes?: TileflowProjectThemes;
-    manifestUrl?: string;
-    preferLocalDev?: boolean;
     alt?: string;
     center?: [number, number];
     zoom?: number;
@@ -25,10 +26,55 @@ type MapProps = {
     imageLoading?: ImgHTMLAttributes<HTMLImageElement>['loading'];
     interactive?: boolean;
     mapOptions?: TileflowMapOptions;
-    markers?: MapMarker[];
     analytics?: TileflowAnalytics;
     onLoad?: (map: Map$1) => void;
+    onThemeChange?: (transition: TileflowThemeTransition) => void;
+};
+type TileflowAnnotationInputProps<TAnnotation extends TileflowAnnotation> = Readonly<{
+    annotations?: readonly TAnnotation[];
+    markers?: never;
+}> | Readonly<{
+    annotations?: never;
+    markers?: readonly MapMarker[];
+}>;
+type TileflowInteractionStateInputProps = Readonly<{
+    defaultInteractionState?: never;
+    interactionState?: TileflowInteractionState;
+}> | Readonly<{
+    defaultInteractionState?: TileflowInteractionState;
+    interactionState?: never;
+}>;
+type TileflowInteractionRendererProps<TAnnotation extends TileflowAnnotation> = Readonly<{
+    interactions?: never;
+    renderPopup?: TileflowAnnotationRenderer<TAnnotation>;
+    renderTooltip?: TileflowAnnotationRenderer<TAnnotation>;
+}> | Readonly<{
+    interactions: readonly TileflowInteractionBinding[];
+    renderPopup?: TileflowInteractionRenderer<TAnnotation>;
+    renderTooltip?: TileflowInteractionRenderer<TAnnotation>;
+}>;
+type MapInteractiveProps<TAnnotation extends TileflowAnnotation> = MapSharedProps & TileflowAnnotationInputProps<TAnnotation> & TileflowInteractionStateInputProps & TileflowInteractionRendererProps<TAnnotation> & {
+    mode?: 'interactive';
+    onInteractionDiagnostic?: (diagnostic: TileflowInteractionDiagnostic) => void;
+    onInteractionEvent?: (event: TileflowInteractionEvent<TAnnotation>) => void;
+    onInteractionStateChange?: (state: TileflowInteractionState) => void;
+    renderMarker?: TileflowAnnotationRenderer<TAnnotation>;
+};
+type MapImageProps = MapSharedProps & {
+    annotations?: never;
+    defaultInteractionState?: never;
+    interactionState?: never;
+    interactions?: never;
+    markers?: never;
+    mode: 'image';
+    onInteractionDiagnostic?: never;
+    onInteractionEvent?: never;
+    onInteractionStateChange?: never;
+    renderMarker?: never;
+    renderPopup?: never;
+    renderTooltip?: never;
 };
-declare function Map({ captureId, map: mapName, mode, config, style, styleUrl, imageUrl, styleBaseUrl, themes, manifestUrl, preferLocalDev, alt, center, zoom, className, height, imageLoading, interactive, mapOptions, markers, analytics, onLoad, }: MapProps): react.JSX.Element;
+type MapProps<TAnnotation extends TileflowAnnotation = TileflowAnnotation> = (MapInteractiveProps<TAnnotation> | MapImageProps) & TileflowMapStyleSourceProps;
+declare function Map<TAnnotation extends TileflowAnnotation = TileflowAnnotation>(props: MapProps<TAnnotation>): react.JSX.Element;
 
-export { Map, type MapMarker, type MapProps, type TileflowMapOptions };
+export { Map, type MapMarker, type MapProps, type TileflowAnnotationRenderer, type TileflowInteractionRenderer, type TileflowMapOptions, type TileflowMapSource };