@tomtom-org/maps-sdk-plugin-agent-toolkit 0.8.0 → 0.9.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1 +1 @@
1
- {"version":3,"file":"worker-libs-CRfkKDM6.js","names":["turfUmd","h3Umd","sdkUtilsSource","sandboxLibrarySource"],"sources":["../src/tools/shared/sandbox/worker-libs.ts"],"sourcesContent":["/**\n * @module agent-toolkit-tools\n *\n * Zero-config library source for the iframe-worker sandbox. The worker needs\n * `turf` / `h3` as a self-contained string (it can't `import` the host app's\n * peer-dep modules across the worker boundary), so we inline their published\n * UMD bundles via Vite `?raw`. Each UMD attaches to the worker's global\n * (`self.turf` / `self.h3`) when evaluated.\n *\n * This module is **dynamically imported** by the executor only when iframe-worker\n * mode actually runs, so the ~600 KB of UMD source lands in a lazy chunk and\n * never bloats the main entry (where turf / h3 stay externalized peer deps).\n *\n * `sandbox-turf-umd` / `sandbox-h3-umd` are build-time aliases (see\n * `vite-sandbox-build.ts`) pointing at `@turf/turf/turf.min.js` and\n * `h3-js/dist/h3-js.umd.js`. Both bypass peer-dep externalization so the `?raw`\n * import is inlined as text rather than kept as a runtime module import (which would\n * resolve to the module object, not its source). turf additionally needs the alias\n * because its `exports` map blocks importing the UMD subpath directly.\n */\n\nimport h3Umd from 'sandbox-h3-umd?raw';\nimport turfUmd from 'sandbox-turf-umd?raw';\n// Bundled SDK worker-utilities IIFE (`routeUtils`, …) from the build-time virtual\n// module. Evaluated AFTER turf so it can read `self.turf`; assigns `self.routeUtils`\n// (and any future groups). See the `sandbox-sdk-utils` plugin in `vite-sandbox-build.ts`\n// and `sdk-utils-worker-entry.ts`.\nimport { source as sdkUtilsSource } from 'virtual:sandbox-sdk-utils';\n\n/**\n * Concatenated turf + h3 UMD source plus the bundled SDK worker-utilities IIFE.\n * Evaluated at the top of the sandbox worker, it defines `self.turf`, `self.h3`, and\n * the SDK utility groups (`self.routeUtils`, …) for the generated code to use. Order\n * matters: turf first, since `routeUtils` reads `self.turf`.\n *\n * @ignore\n */\nexport const sandboxLibrarySource = `${turfUmd}\\n;${h3Umd}\\n;${sdkUtilsSource}`;\n"],"mappings":"IAqCaG,EAAuB"}
1
+ {"version":3,"file":"worker-libs-Cn3Jhheb.js","names":["turfUmd","h3Umd","sdkUtilsSource","sandboxLibrarySource"],"sources":["../src/tools/shared/sandbox/worker-libs.ts"],"sourcesContent":["/**\n * @module agent-toolkit-tools\n *\n * Zero-config library source for the iframe-worker sandbox. The worker needs\n * `turf` / `h3` as a self-contained string (it can't `import` the host app's\n * peer-dep modules across the worker boundary), so we inline their published\n * UMD bundles via Vite `?raw`. Each UMD attaches to the worker's global\n * (`self.turf` / `self.h3`) when evaluated.\n *\n * This module is **dynamically imported** by the executor only when iframe-worker\n * mode actually runs, so the ~600 KB of UMD source lands in a lazy chunk and\n * never bloats the main entry (where turf / h3 stay externalized peer deps).\n *\n * `sandbox-turf-umd` / `sandbox-h3-umd` are build-time aliases (see\n * `vite-sandbox-build.ts`) pointing at `@turf/turf/turf.min.js` and\n * `h3-js/dist/h3-js.umd.js`. Both bypass peer-dep externalization so the `?raw`\n * import is inlined as text rather than kept as a runtime module import (which would\n * resolve to the module object, not its source). turf additionally needs the alias\n * because its `exports` map blocks importing the UMD subpath directly.\n */\n\nimport h3Umd from 'sandbox-h3-umd?raw';\nimport turfUmd from 'sandbox-turf-umd?raw';\n// Bundled SDK worker-utilities IIFE (`routeUtils`, …) from the build-time virtual\n// module. Evaluated AFTER turf so it can read `self.turf`; assigns `self.routeUtils`\n// (and any future groups). See the `sandbox-sdk-utils` plugin in `vite-sandbox-build.ts`\n// and `sdk-utils-worker-entry.ts`.\nimport { source as sdkUtilsSource } from 'virtual:sandbox-sdk-utils';\n\n/**\n * Concatenated turf + h3 UMD source plus the bundled SDK worker-utilities IIFE.\n * Evaluated at the top of the sandbox worker, it defines `self.turf`, `self.h3`, and\n * the SDK utility groups (`self.routeUtils`, …) for the generated code to use. Order\n * matters: turf first, since `routeUtils` reads `self.turf`.\n *\n * @ignore\n */\nexport const sandboxLibrarySource = `${turfUmd}\\n;${h3Umd}\\n;${sdkUtilsSource}`;\n"],"mappings":"IAqCaG,EAAuB"}
package/package.json CHANGED
@@ -2,13 +2,13 @@
2
2
  "name": "@tomtom-org/maps-sdk-plugin-agent-toolkit",
3
3
  "author": "TomTom International B.V.",
4
4
  "license": "See in LICENSE.txt",
5
- "version": "0.8.0",
5
+ "version": "0.9.0",
6
6
  "type": "module",
7
7
  "description": "Agent toolkit plugin for TomTom Maps SDK JS using Vercel AI SDK",
8
8
  "types": "dist/index.d.ts",
9
9
  "peerDependencies": {
10
- "@tomtom-org/maps-sdk": ">=0.58.0 <1.0.0",
11
- "@tomtom-org/maps-sdk-plugin-map-theme": ">=0.1.0",
10
+ "@tomtom-org/maps-sdk": ">=0.59.0 <1.0.0",
11
+ "@tomtom-org/maps-sdk-plugin-map-theme": ">=0.2.0",
12
12
  "@turf/turf": "^7.4.0",
13
13
  "ai": "^6.0.291",
14
14
  "chart.js": "^4.5.1",
@@ -32,8 +32,8 @@
32
32
  "vite": "^8.3.1",
33
33
  "vitest": "^4.1.11",
34
34
  "@testing/agent-tool-calling": "0.0.0",
35
- "@tomtom-org/maps-sdk": "0.58.0",
36
- "@tomtom-org/maps-sdk-plugin-map-theme": "0.1.0"
35
+ "@tomtom-org/maps-sdk": "0.59.0",
36
+ "@tomtom-org/maps-sdk-plugin-map-theme": "0.2.0"
37
37
  },
38
38
  "files": [
39
39
  "dist",