@squawk/airways
Advanced tools
+5
-1
| { | ||
| "name": "@squawk/airways", | ||
| "version": "0.3.5", | ||
| "version": "0.4.0", | ||
| "type": "module", | ||
@@ -24,2 +24,6 @@ "description": "Airway lookup, traversal, and expansion by designation, fix, or search", | ||
| "import": "./dist/index.js" | ||
| }, | ||
| "./browser": { | ||
| "types": "./dist/index.d.ts", | ||
| "import": "./dist/index.js" | ||
| } | ||
@@ -26,0 +30,0 @@ }, |
+14
-0
@@ -50,2 +50,16 @@ <h1><img src="../../../assets/squawk-logo.svg" alt="squawk logo" width="48" height="48" style="vertical-align: middle"> @squawk/airways</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/airway-data/browser`: | ||
| ```typescript | ||
| import { loadUsBundledAirways } from '@squawk/airway-data/browser'; | ||
| import { createAirwayResolver } from '@squawk/airways/browser'; | ||
| const dataset = await loadUsBundledAirways(); | ||
| const resolver = createAirwayResolver({ 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 | ||
@@ -52,0 +66,0 @@ |
15999
4.68%123
12.84%