@squawk/airports
Advanced tools
+5
-1
| { | ||
| "name": "@squawk/airports", | ||
| "version": "0.5.4", | ||
| "version": "0.6.0", | ||
| "type": "module", | ||
@@ -24,2 +24,6 @@ "description": "Pure logic library for querying US airport data by identifier, location, or name", | ||
| "import": "./dist/index.js" | ||
| }, | ||
| "./browser": { | ||
| "types": "./dist/index.d.ts", | ||
| "import": "./dist/index.js" | ||
| } | ||
@@ -26,0 +30,0 @@ }, |
+14
-0
@@ -43,2 +43,16 @@ <h1><img src="../../../assets/squawk-logo.svg" alt="squawk logo" width="48" height="48" style="vertical-align: middle"> @squawk/airports</h1> | ||
| ## Browser / SPA usage | ||
| The resolver factory has no Node-specific imports and ships an explicit `/browser` subpath for SPAs and edge runtimes. Pair it with `@squawk/airport-data/browser`: | ||
| ```typescript | ||
| import { loadUsBundledAirports } from '@squawk/airport-data/browser'; | ||
| import { createAirportResolver } from '@squawk/airports/browser'; | ||
| const dataset = await loadUsBundledAirports(); | ||
| const resolver = createAirportResolver({ data: dataset.records }); | ||
| ``` | ||
| The `/browser` entry is identical to the main entry; the separate subpath exists so browser support is an explicit, `publint`-verified part of the public API surface. | ||
| ## API | ||
@@ -45,0 +59,0 @@ |
16097
4.7%151
10.22%