feat(core): ⚡️ update node dependencies, refactor utils, and document breaking changes

* Update Node.js dependencies and adjust `peer` flags in `package-lock.json` for improved compatibility.
* Refactor utility functions: export `get` and `set` from `MappingUtils.ts` and update imports in `XMLParser.ts`.
* Move `chunk` utility in `CaaSMapper.ts` for consistency.
* Update `.env.template` with new `INTEGRATION_TEST_TENANT_ID` variable.
* Update package metadata: bump version to 11.0.0, update authors/contributors.
* Add breaking changes and migration guide to `CHANGELOG.md`; remove migration guide from `README.md`.

Signed-off-by: Justin Wiegmann <wiegmann@e-spirit.com>

Author: spirit-wiegmann

CHANGELOG.md

@@ -1,3 +1,53 @@
+## BREAKING CHANGES
+
+### Migrating to v11.0.0
+
+This version contains breaking changes. Please read the following migration guide carefully.
+
+#### 1. CaaSEventStream - Lazy Loading (Breaking Change)
+
+The `CaaSEventStream` export has been changed to use lazy loading to prevent browser bundling issues with the `better-sse` dependency.
+
+**Before (v10.x):**
+```typescript
+import { CaaSEventStream } from 'fsxa-api'
+
+const handler = CaaSEventStream.eventStreamHandler(api)
+```
+
+**After (v11.x):**
+```typescript
+import { CaaSEventStream } from 'fsxa-api'
+
+// Now requires async/await
+const handler = await CaaSEventStream.getEventStreamHandler(api)
+```
+
+**Key Changes:**
+- `CaaSEventStream.eventStreamHandler()` is now `CaaSEventStream.getEventStreamHandler()` and returns a Promise
+- The module is dynamically imported only when called (server-side), preventing `better-sse` from being bundled in browser builds
+- Browser code can safely import `fsxa-api` without errors, as long as `getEventStreamHandler()` is only called on the server
+
+#### 2. Default maxReferenceDepth Changed (Breaking Change)
+
+The default value for `maxReferenceDepth` has been reduced from **10** to **2** for performance optimization.
+
+**Impact:** If your application relies on deeply nested references being resolved automatically, you may need to explicitly set a higher value.
+
+**Migration:**
+```typescript
+const config = {
+  apikey: 'your-api-key',
+  caasURL: 'https://your.caas.url',
+  // ... other config options
+  maxReferenceDepth: 10, // Explicitly set if you need the old behavior
+}
+
+const api = new FSXARemoteApi(config)
+```
+
+**Recommendation:** The new default of 2 is sufficient for most use cases and improves performance. Only increase this value if you specifically need deeper reference resolution.
+
 # [10.24.0](https://github.com/e-Spirit/javascript-content-api-library/compare/v10.23.0...v10.24.0) (2025-09-22)
 
 

README.md

@@ -25,56 +25,6 @@ Relying solely on the provided code without thorough validation and possible ext
 Features marked as experimental are subject to change as long as they remain in the experimental state.
 Breaking changes to experimental features are not reflected in a major version changes.
 
-## Migration Guide
-
-### Migrating to v11.0.0
-
-This version contains breaking changes. Please read the following migration guide carefully.
-
-#### 1. CaaSEventStream - Lazy Loading (Breaking Change)
-
-The `CaaSEventStream` export has been changed to use lazy loading to prevent browser bundling issues with the `better-sse` dependency.
-
-**Before (v10.x):**
-```typescript
-import { CaaSEventStream } from 'fsxa-api'
-
-const handler = CaaSEventStream.eventStreamHandler(api)
-```
-
-**After (v11.x):**
-```typescript
-import { CaaSEventStream } from 'fsxa-api'
-
-// Now requires async/await
-const handler = await CaaSEventStream.getEventStreamHandler(api)
-```
-
-**Key Changes:**
-- `CaaSEventStream.eventStreamHandler()` is now `CaaSEventStream.getEventStreamHandler()` and returns a Promise
-- The module is dynamically imported only when called (server-side), preventing `better-sse` from being bundled in browser builds
-- Browser code can safely import `fsxa-api` without errors, as long as `getEventStreamHandler()` is only called on the server
-
-#### 2. Default maxReferenceDepth Changed (Breaking Change)
-
-The default value for `maxReferenceDepth` has been reduced from **10** to **2** for performance optimization.
-
-**Impact:** If your application relies on deeply nested references being resolved automatically, you may need to explicitly set a higher value.
-
-**Migration:**
-```typescript
-const config = {
-  apikey: 'your-api-key',
-  caasURL: 'https://your.caas.url',
-  // ... other config options
-  maxReferenceDepth: 10, // Explicitly set if you need the old behavior
-}
-
-const api = new FSXARemoteApi(config)
-```
-
-**Recommendation:** The new default of 2 is sufficient for most use cases and improves performance. Only increase this value if you specifically need deeper reference resolution.
-
 ## Methods
 
 In this section all available methods will be explained using examples.

integrationtests/.env.template

@@ -1,3 +1,4 @@
 INTEGRATION_TEST_API_KEY=xxxxxxxx-xxxx-xxxx-xxxxxxxx
 INTEGRATION_TEST_CAAS=https://your-caas-api.e-spirit.cloud
-INTEGRATION_TEST_NAVIGATION_SERVICE=https://your-navigation-service.e-spirit.cloud
+INTEGRATION_TEST_NAVIGATION_SERVICE=https://your-navigation-service.e-spirit.cloud
+INTEGRATION_TEST_TENANT_ID=fsxa-api-integration-test