also looking at this
fix(sdk): ship declarations that resolve under node16/nodenext
#42
43 files
+196
-137
| @@ -10,8 +10,8 @@ | ||
| 10 | 10 | // package root, so we don't pull the entire `craft-native` surface |
| 11 | 11 | // (including unrelated stx-templated sidebar files) through the type |
| 12 | 12 | // checker. The public API of the bridge is stable, so this is fine. |
| 13 | import type { NativeBridge } from '../../typescript/src/bridge/core' | |
| 14 | import { getBridge } from '../../typescript/src/bridge/core' | |
| 13 | import type { NativeBridge } from '../../typescript/src/bridge/core.js' | |
| 14 | import { getBridge } from '../../typescript/src/bridge/core.js' | |
| 15 | 15 | import type { TsMap } from 'ts-maps' |
| 16 | 16 | import { createMap, tileLayer } from 'ts-maps' |
| 17 | 17 | import { |
| @@ -23,12 +23,12 @@ import { | ||
| 23 | 23 | craftPolylineToPolyline, |
| 24 | 24 | craftRegionToBounds, |
| 25 | 25 | latLngToCraftCoord, |
| 26 | } from './adapters' | |
| 26 | } from './adapters.js' | |
| 27 | 27 | import type { |
| 28 | 28 | MapBridgeEvent, |
| 29 | 29 | TypedMapBridgeRequest, |
| 30 | } from './bridge-protocol' | |
| 31 | import { BRIDGE_NAMESPACE, mapEventName } from './bridge-protocol' | |
| 30 | } from './bridge-protocol.js' | |
| 31 | import { BRIDGE_NAMESPACE, mapEventName } from './bridge-protocol.js' | |
| 32 | 32 | import type { |
| 33 | 33 | Coordinate, |
| 34 | 34 | MapCamera, |
| @@ -38,8 +38,8 @@ import type { | ||
| 38 | 38 | MapPolygon, |
| 39 | 39 | MapPolyline, |
| 40 | 40 | MapRegion, |
| 41 | } from './types' | |
| 42 | import { defaultMapCamera, defaultMapConfiguration } from './types' | |
| 41 | } from './types.js' | |
| 42 | import { defaultMapCamera, defaultMapConfiguration } from './types.js' | |
| 43 | 43 | |
| 44 | 44 | // Monotonic counter — same pattern as `components/native.ts` in |
| 45 | 45 | // `craft-native` — so multiple map views created in the same tick |