@inploi/plugin-job-search 9.0.3 → 9.0.4

package/README.md

@@ -64,10 +64,12 @@ its observers, event listeners and scoped stylesheet through the control's `onRe
 `resolveMapStyle` returns `{ url, unmapped? }`, and throws for an unsupported format; callers can use
 `unmapped` to identify a legacy style that needs migrating.
 Under TypeScript's `node16` resolution, `utils`' types fail to type-check with `skipLibCheck: false`. The cause is
-MapLibre's own declarations: `createMapAttribution` takes MapLibre's `Map`, and MapLibre's dependency
-`@maplibre/geojson-vt` imports without file extensions. `skipLibCheck: true` or `bundler` resolution avoids it.
-Separately, `mapbox-gl` installs a stub `@types/mapbox__point-geometry` that breaks TypeScript's automatic global
-types. Consumers who hit TS2688 can list their global types explicitly, for example `"types": ["geojson"]`.
+MapLibre's own declarations, which `createMapAttribution` reaches through MapLibre's `Map`: its dependencies
+`@maplibre/geojson-vt` and `@maplibre/vt-pbf` import without file extensions (TS2834), and `maplibre-gl`'s CommonJS
+declarations import ES modules without `resolution-mode` (TS1479, TS1542). `skipLibCheck: true` or `bundler`
+resolution avoids it. Separately, `mapbox-gl` installs a stub `@types/mapbox__point-geometry` that breaks
+TypeScript's automatic global types. Consumers who hit TS2688 can list their global types explicitly, for example
+`"types": ["geojson"]`. CI's [packed types](../../docs/ci.md#packed-types) check allows exactly these upstream errors.
 MapLibre's cooperative-gesture hints use the plugin's `map_gesture_windows`, `map_gesture_mac` and
 `map_gesture_mobile` terms, so embeds can localise them through `terms`.