Sign In

@squawk/airways

Package Overview
Dependencies
Maintainers
1
Versions
19
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@squawk/airways - npm Package Compare versions

Comparing version
0.3.5
to
0.4.0
+5
-1
package.json
{
"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 @@ },

@@ -50,2 +50,16 @@ <h1><img src="../../../assets/squawk-logo.svg" alt="squawk logo" width="48" height="48" style="vertical-align: middle">&nbsp; @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 @@