@fluidframework/aqueduct 2.30.0 → 2.31.1

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # @fluidframework/aqueduct
 
+## 2.31.0
+
+Dependency updates only.
+
 ## 2.30.0
 
 Dependency updates only.
@@ -20,27 +24,27 @@ Dependency updates only.
 
 ### Minor Changes
 
--   The ContainerRuntime class has been removed ([#23341](https://github.com/microsoft/FluidFramework/pull/23341)) [61ba06aa98](https://github.com/microsoft/FluidFramework/commit/61ba06aa9881c30ffeeedcaaede9c5a1a0c81abd)
+- The ContainerRuntime class has been removed ([#23341](https://github.com/microsoft/FluidFramework/pull/23341)) [61ba06aa98](https://github.com/microsoft/FluidFramework/commit/61ba06aa9881c30ffeeedcaaede9c5a1a0c81abd)
 
-    The `ContainerRuntime` class was [deprecated in version 2.12.0](https://github.com/microsoft/FluidFramework/releases/tag/client_v2.12.0#user-content-the-containerruntime-class-is-now-deprecated-23331) and has been removed.
-    Use `IContainerRuntime` to replace type usages and use the free function `loadContainerRuntime` to replace usages of the static method `ContainerRuntime.loadRuntime`.
+  The `ContainerRuntime` class was [deprecated in version 2.12.0](https://github.com/microsoft/FluidFramework/releases/tag/client_v2.12.0#user-content-the-containerruntime-class-is-now-deprecated-23331) and has been removed.
+  Use `IContainerRuntime` to replace type usages and use the free function `loadContainerRuntime` to replace usages of the static method `ContainerRuntime.loadRuntime`.
 
-    See the [deprecation
-    announcement](https://github.com/microsoft/FluidFramework/releases/tag/client_v2.12.0#user-content-the-containerruntime-class-is-now-deprecated-23331)
-    for more details about how to update existing code.
+  See the [deprecation
+  announcement](https://github.com/microsoft/FluidFramework/releases/tag/client_v2.12.0#user-content-the-containerruntime-class-is-now-deprecated-23331)
+  for more details about how to update existing code.
 
--   The createDataStoreWithProps APIs on ContainerRuntime and IContainerRuntimeBase have been removed ([#22996](https://github.com/microsoft/FluidFramework/pull/22996)) [bd243fb292](https://github.com/microsoft/FluidFramework/commit/bd243fb2927915d87c42486e21ee0c990962a9a7)
+- The createDataStoreWithProps APIs on ContainerRuntime and IContainerRuntimeBase have been removed ([#22996](https://github.com/microsoft/FluidFramework/pull/22996)) [bd243fb292](https://github.com/microsoft/FluidFramework/commit/bd243fb2927915d87c42486e21ee0c990962a9a7)
 
-    `ContainerRuntime.createDataStoreWithProps` and `IContainerRuntimeBase.createDataStoreWithProps`
-    were [deprecated in version 0.25.0](https://github.com/microsoft/FluidFramework/blob/main/BREAKING.md#icontainerruntimebase_createdatastorewithprops-is-removed) and have been removed.
+  `ContainerRuntime.createDataStoreWithProps` and `IContainerRuntimeBase.createDataStoreWithProps`
+  were [deprecated in version 0.25.0](https://github.com/microsoft/FluidFramework/blob/main/BREAKING.md#icontainerruntimebase_createdatastorewithprops-is-removed) and have been removed.
 
-    Replace uses of these APIs with `PureDataObjectFactory.createInstanceWithDataStore` and pass in props via the `initialState`
-    parameter.
+  Replace uses of these APIs with `PureDataObjectFactory.createInstanceWithDataStore` and pass in props via the `initialState`
+  parameter.
 
-    These changes were originally announced in version 0.25.0. See the following issues for more details:
+  These changes were originally announced in version 0.25.0. See the following issues for more details:
 
-    -   [#1537](https://github.com/microsoft/FluidFramework/issues/1537)
-    -   [#2931](https://github.com/microsoft/FluidFramework/pull/2931)
+  - [#1537](https://github.com/microsoft/FluidFramework/issues/1537)
+  - [#2931](https://github.com/microsoft/FluidFramework/pull/2931)
 
 ## 2.13.0
 
@@ -50,22 +54,22 @@ Dependency updates only.
 
 ### Minor Changes
 
--   The ContainerRuntime class is now deprecated ([#23331](https://github.com/microsoft/FluidFramework/pull/23331)) [dc48446d7c](https://github.com/microsoft/FluidFramework/commit/dc48446d7c4914aca2a76095205975824aac1ba5)
+- The ContainerRuntime class is now deprecated ([#23331](https://github.com/microsoft/FluidFramework/pull/23331)) [dc48446d7c](https://github.com/microsoft/FluidFramework/commit/dc48446d7c4914aca2a76095205975824aac1ba5)
 
-    The class `ContainerRuntime` is deprecated and will no longer be exported starting in version 2.20.0.
+  The class `ContainerRuntime` is deprecated and will no longer be exported starting in version 2.20.0.
 
-    There are two possible migration paths to stop using `ContainerRuntime`:
+  There are two possible migration paths to stop using `ContainerRuntime`:
 
-    -   When using it as a type, replace it with an interface like `IContainerRuntime`
-    -   When using the static function `ContainerRuntime.loadRuntime` replace it with the free function `loadContainerRuntime`.
+  - When using it as a type, replace it with an interface like `IContainerRuntime`
+  - When using the static function `ContainerRuntime.loadRuntime` replace it with the free function `loadContainerRuntime`.
 
-    `BaseContainerRuntimeFactory` has some changes as well, since it exposed `ContainerRuntime` in several function signatures:
+  `BaseContainerRuntimeFactory` has some changes as well, since it exposed `ContainerRuntime` in several function signatures:
 
-    -   `instantiateFirstTime` - Takes the wider type `IContainerRuntime` instead of `ContainerRuntime`
-    -   `instantiateFromExisting` - Takes the wider type `IContainerRuntime` instead of `ContainerRuntime`
-    -   `preInitialize` - deprecated as well, since it returns `ContainerRuntime`
+  - `instantiateFirstTime` - Takes the wider type `IContainerRuntime` instead of `ContainerRuntime`
+  - `instantiateFromExisting` - Takes the wider type `IContainerRuntime` instead of `ContainerRuntime`
+  - `preInitialize` - deprecated as well, since it returns `ContainerRuntime`
 
-    These functions should never be called directly anyway - use `BaseContainerRuntimeFactory.instantiateRuntime` instead.
+  These functions should never be called directly anyway - use `BaseContainerRuntimeFactory.instantiateRuntime` instead.
 
 ## 2.11.0
 
@@ -75,19 +79,19 @@ Dependency updates only.
 
 ### Minor Changes
 
--   The inbound and outbound properties have been removed from IDeltaManager ([#22282](https://github.com/microsoft/FluidFramework/pull/22282)) [45a57693f2](https://github.com/microsoft/FluidFramework/commit/45a57693f291e0dc5e91af7f29a9b9c8f82dfad5)
+- The inbound and outbound properties have been removed from IDeltaManager ([#22282](https://github.com/microsoft/FluidFramework/pull/22282)) [45a57693f2](https://github.com/microsoft/FluidFramework/commit/45a57693f291e0dc5e91af7f29a9b9c8f82dfad5)
 
-    The inbound and outbound properties were [deprecated in version 2.0.0-rc.2.0.0](https://github.com/microsoft/FluidFramework/blob/main/RELEASE_NOTES/2.0.0-rc.2.0.0.md#container-definitions-deprecate-ideltamanagerinbound-and-ideltamanageroutbound) and have been removed from `IDeltaManager`.
+  The inbound and outbound properties were [deprecated in version 2.0.0-rc.2.0.0](https://github.com/microsoft/FluidFramework/blob/main/RELEASE_NOTES/2.0.0-rc.2.0.0.md#container-definitions-deprecate-ideltamanagerinbound-and-ideltamanageroutbound) and have been removed from `IDeltaManager`.
 
-    `IDeltaManager.inbound` contained functionality that could break core runtime features such as summarization and processing batches if used improperly. Data loss or corruption could occur when `IDeltaManger.inbound.pause()` or `IDeltaManager.inbound.resume()` were called.
+  `IDeltaManager.inbound` contained functionality that could break core runtime features such as summarization and processing batches if used improperly. Data loss or corruption could occur when `IDeltaManger.inbound.pause()` or `IDeltaManager.inbound.resume()` were called.
 
-    Similarly, `IDeltaManager.outbound` contained functionality that could break core runtime features such as generation of batches and chunking. Data loss or corruption could occur when `IDeltaManger.inbound.pause()` or `IDeltaManager.inbound.resume()` were called.
+  Similarly, `IDeltaManager.outbound` contained functionality that could break core runtime features such as generation of batches and chunking. Data loss or corruption could occur when `IDeltaManger.inbound.pause()` or `IDeltaManager.inbound.resume()` were called.
 
-    #### Alternatives
+  #### Alternatives
 
-    -   Alternatives to `IDeltaManager.inbound.on("op", ...)` are `IDeltaManager.on("op", ...)`
-    -   Alternatives to calling `IDeltaManager.inbound.pause`, `IDeltaManager.outbound.pause` for `IContainer` disconnect use `IContainer.disconnect`.
-    -   Alternatives to calling `IDeltaManager.inbound.resume`, `IDeltaManager.outbound.resume` for `IContainer` reconnect use `IContainer.connect`.
+  - Alternatives to `IDeltaManager.inbound.on("op", ...)` are `IDeltaManager.on("op", ...)`
+  - Alternatives to calling `IDeltaManager.inbound.pause`, `IDeltaManager.outbound.pause` for `IContainer` disconnect use `IContainer.disconnect`.
+  - Alternatives to calling `IDeltaManager.inbound.resume`, `IDeltaManager.outbound.resume` for `IContainer` reconnect use `IContainer.connect`.
 
 ## 2.5.0
 
@@ -113,9 +117,9 @@ Dependency updates only.
 
 ### Minor Changes
 
--   Update to TypeScript 5.4 ([#21214](https://github.com/microsoft/FluidFramework/pull/21214)) [0e6256c722](https://github.com/microsoft/FluidFramework/commit/0e6256c722d8bf024f4325bf02547daeeb18bfa6)
+- Update to TypeScript 5.4 ([#21214](https://github.com/microsoft/FluidFramework/pull/21214)) [0e6256c722](https://github.com/microsoft/FluidFramework/commit/0e6256c722d8bf024f4325bf02547daeeb18bfa6)
 
-    Update package implementations to use TypeScript 5.4.5.
+  Update package implementations to use TypeScript 5.4.5.
 
 ## 2.0.0-rc.4.0.0
 
@@ -125,54 +129,54 @@ Dependency updates only.
 
 ### Major Changes
 
--   Packages now use package.json "exports" and require modern module resolution [97d68aa06b](https://github.com/microsoft/FluidFramework/commit/97d68aa06bd5c022ecb026655814aea222a062ae)
+- Packages now use package.json "exports" and require modern module resolution [97d68aa06b](https://github.com/microsoft/FluidFramework/commit/97d68aa06bd5c022ecb026655814aea222a062ae)
 
-    Fluid Framework packages have been updated to use the [package.json "exports"
-    field](https://nodejs.org/docs/latest-v18.x/api/packages.html#exports) to define explicit entry points for both
-    TypeScript types and implementation code.
+  Fluid Framework packages have been updated to use the [package.json "exports"
+  field](https://nodejs.org/docs/latest-v18.x/api/packages.html#exports) to define explicit entry points for both
+  TypeScript types and implementation code.
 
-    This means that using Fluid Framework packages require the following TypeScript settings in tsconfig.json:
+  This means that using Fluid Framework packages require the following TypeScript settings in tsconfig.json:
 
-    -   `"moduleResolution": "Node16"` with `"module": "Node16"`
-    -   `"moduleResolution": "Bundler"` with `"module": "ESNext"`
+  - `"moduleResolution": "Node16"` with `"module": "Node16"`
+  - `"moduleResolution": "Bundler"` with `"module": "ESNext"`
 
-    We recommend using Node16/Node16 unless absolutely necessary. That will produce transpiled JavaScript that is suitable
-    for use with modern versions of Node.js _and_ Bundlers.
-    [See the TypeScript documentation](https://www.typescriptlang.org/tsconfig#moduleResolution) for more information
-    regarding the module and moduleResolution options.
+  We recommend using Node16/Node16 unless absolutely necessary. That will produce transpiled JavaScript that is suitable
+  for use with modern versions of Node.js _and_ Bundlers.
+  [See the TypeScript documentation](https://www.typescriptlang.org/tsconfig#moduleResolution) for more information
+  regarding the module and moduleResolution options.
 
-    **Node10 moduleResolution is not supported; it does not support Fluid Framework's API structuring pattern that is used
-    to distinguish stable APIs from those that are in development.**
+  **Node10 moduleResolution is not supported; it does not support Fluid Framework's API structuring pattern that is used
+  to distinguish stable APIs from those that are in development.**
 
 ## 2.0.0-rc.2.0.0
 
 ### Minor Changes
 
--   aqueduct: Deprecated PureDataObjectFactory.createRootInstance and replaced with PureDataObjectFactory.createInstanceWithDataStore ([#19471](https://github.com/microsoft/FluidFramework/issues/19471)) [0a79375ccb](https://github.com/microsoft/FluidFramework/commits/0a79375ccb523658a2565b8796fa06ec45a69394)
+- aqueduct: Deprecated PureDataObjectFactory.createRootInstance and replaced with PureDataObjectFactory.createInstanceWithDataStore ([#19471](https://github.com/microsoft/FluidFramework/issues/19471)) [0a79375ccb](https://github.com/microsoft/FluidFramework/commits/0a79375ccb523658a2565b8796fa06ec45a69394)
 
-    ### Deprecated: PureDataObjectFactory.createRootInstance
+  ### Deprecated: PureDataObjectFactory.createRootInstance
 
-    This was deprecated because `PureDataObjectFactory.createRootInstance` has an issue at scale.
-    `PureDataObjectFactory.createRootInstance` used the old method of creating `PureDataObject`s with names. The issue was
-    that simultaneous creations could happen, and the old api had no good way of dealing with those types of collisions.
-    This version slightly improved it by resolving those collisions by assuming whatever datastore was created with the
-    alias or `rootDataStoreId` would just return that datastore. This will work for developers who expect the same type of
-    `PureDataObject` to be returned from the `createRootInstance` api, but if a potentially different `PureDataObject`
-    would be returned, then this api would give you the wrong typing.
+  This was deprecated because `PureDataObjectFactory.createRootInstance` has an issue at scale.
+  `PureDataObjectFactory.createRootInstance` used the old method of creating `PureDataObject`s with names. The issue was
+  that simultaneous creations could happen, and the old api had no good way of dealing with those types of collisions.
+  This version slightly improved it by resolving those collisions by assuming whatever datastore was created with the
+  alias or `rootDataStoreId` would just return that datastore. This will work for developers who expect the same type of
+  `PureDataObject` to be returned from the `createRootInstance` api, but if a potentially different `PureDataObject`
+  would be returned, then this api would give you the wrong typing.
 
-    For a replacement api see `PureDataObjectFactory.createInstanceWithDataStore`.
+  For a replacement api see `PureDataObjectFactory.createInstanceWithDataStore`.
 
-    ### New method PureDataObjectFactory.createInstanceWithDataStore
+  ### New method PureDataObjectFactory.createInstanceWithDataStore
 
-    This was done as a replacement of `PureDataObjectFactory.createRootInstance`. This exposes the `IDataStore` interface
-    in the form of `[PureDataObject, IDataStore]`. `IDataStore` provides the opportunity for developers to use the
-    `IDataStore.trySetAlias` method. This can return 3 different scenarios `Success`, `Conflict`, or `AlreadyAliased`.
-    These scenarios can allow the developer to handle conflicts as they wish.
+  This was done as a replacement of `PureDataObjectFactory.createRootInstance`. This exposes the `IDataStore` interface
+  in the form of `[PureDataObject, IDataStore]`. `IDataStore` provides the opportunity for developers to use the
+  `IDataStore.trySetAlias` method. This can return 3 different scenarios `Success`, `Conflict`, or `AlreadyAliased`.
+  These scenarios can allow the developer to handle conflicts as they wish.
 
--   aqueduct: PureDataObjectFactory.instantiateDataStore now returns IFluidDataStoreChannel ([#19353](https://github.com/microsoft/FluidFramework/issues/19353)) [3aad53da1e](https://github.com/microsoft/FluidFramework/commits/3aad53da1ee8c4079d4f3b4a096361d23e0725ab)
+- aqueduct: PureDataObjectFactory.instantiateDataStore now returns IFluidDataStoreChannel ([#19353](https://github.com/microsoft/FluidFramework/issues/19353)) [3aad53da1e](https://github.com/microsoft/FluidFramework/commits/3aad53da1ee8c4079d4f3b4a096361d23e0725ab)
 
-    The return type of `PureDataObjectFactory.instantiateDataStore` was changed from `FluidDataStoreRuntime` to
-    `IFluidDataStoreChannel`.
+  The return type of `PureDataObjectFactory.instantiateDataStore` was changed from `FluidDataStoreRuntime` to
+  `IFluidDataStoreChannel`.
 
 ## 2.0.0-rc.1.0.0
 
@@ -182,57 +186,57 @@ Dependency updates only.
 
 ### Major Changes
 
--   aqueduct: Removed getDefaultObjectFromContainer, getObjectWithIdFromContainer and getObjectFromContainer [9a451d4946](https://github.com/microsoft/FluidFramework/commits/9a451d4946b5c51a52e4d1ab5bf51e7b285b0d74)
+- aqueduct: Removed getDefaultObjectFromContainer, getObjectWithIdFromContainer and getObjectFromContainer [9a451d4946](https://github.com/microsoft/FluidFramework/commits/9a451d4946b5c51a52e4d1ab5bf51e7b285b0d74)
 
-    The `getDefaultObjectFromContainer`, `getObjectWithIdFromContainer` and `getObjectFromContainer` helper methods have been removed from @fluidframework/aqueduct. Please move all code usage to the new `entryPoint` pattern.
+  The `getDefaultObjectFromContainer`, `getObjectWithIdFromContainer` and `getObjectFromContainer` helper methods have been removed from @fluidframework/aqueduct. Please move all code usage to the new `entryPoint` pattern.
 
-    See
-    [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md)
-    for more details.
+  See
+  [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md)
+  for more details.
 
--   data-object-base: Removed IFluidRouter from DataObject interfaces and classes [9a451d4946](https://github.com/microsoft/FluidFramework/commits/9a451d4946b5c51a52e4d1ab5bf51e7b285b0d74)
+- data-object-base: Removed IFluidRouter from DataObject interfaces and classes [9a451d4946](https://github.com/microsoft/FluidFramework/commits/9a451d4946b5c51a52e4d1ab5bf51e7b285b0d74)
 
-    The `IFluidRouter` property has been removed from a number of DataObject related classes:
+  The `IFluidRouter` property has been removed from a number of DataObject related classes:
 
-    -   `PureDataObject`
-    -   `LazyLoadedDataObject`
-    -   `TestFluidObject`
+  - `PureDataObject`
+  - `LazyLoadedDataObject`
+  - `TestFluidObject`
 
-    Please migrate to the new `entryPoint` pattern or use the relevant `request` method as necessary.
+  Please migrate to the new `entryPoint` pattern or use the relevant `request` method as necessary.
 
-    See
-    [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md)
-    for more details.
+  See
+  [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md)
+  for more details.
 
--   aqueduct: Removed IRootDataObjectFactory [9a451d4946](https://github.com/microsoft/FluidFramework/commits/9a451d4946b5c51a52e4d1ab5bf51e7b285b0d74)
+- aqueduct: Removed IRootDataObjectFactory [9a451d4946](https://github.com/microsoft/FluidFramework/commits/9a451d4946b5c51a52e4d1ab5bf51e7b285b0d74)
 
-    The `IRootDataObjectFactory` interface has been removed. Please remove all usage of it.
+  The `IRootDataObjectFactory` interface has been removed. Please remove all usage of it.
 
--   aqueduct: Removed requestHandler utilities [9a451d4946](https://github.com/microsoft/FluidFramework/commits/9a451d4946b5c51a52e4d1ab5bf51e7b285b0d74)
+- aqueduct: Removed requestHandler utilities [9a451d4946](https://github.com/microsoft/FluidFramework/commits/9a451d4946b5c51a52e4d1ab5bf51e7b285b0d74)
 
-    The following `requestHandler` utilities have been removed:
+  The following `requestHandler` utilities have been removed:
 
-    -   `makeModelRequestHandler`
-    -   `defaultFluidObjectRequestHandler`
-    -   `defaultRouteRequestHandler`
-    -   `mountableViewRequestHandler`
-    -   `createFluidObjectResponse`
-    -   `rootDataStoreRequestHandler`
-    -   `handleFromLegacyUri`
-    -   `RuntimeRequestHandlerBuilder`
+  - `makeModelRequestHandler`
+  - `defaultFluidObjectRequestHandler`
+  - `defaultRouteRequestHandler`
+  - `mountableViewRequestHandler`
+  - `createFluidObjectResponse`
+  - `rootDataStoreRequestHandler`
+  - `handleFromLegacyUri`
+  - `RuntimeRequestHandlerBuilder`
 
-    Please migrate all usage to the new `entryPoint` pattern.
+  Please migrate all usage to the new `entryPoint` pattern.
 
-    See [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md) for more details.
+  See [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md) for more details.
 
 ## 2.0.0-internal.7.4.0
 
 ### Minor Changes
 
--   aqueduct: Deprecated IRootDataObjectFactory ([#18565](https://github.com/microsoft/FluidFramework/issues/18565)) [030ab7adf9](https://github.com/microsoft/FluidFramework/commits/030ab7adf991d2d983437544600a191ac15ca5a5)
+- aqueduct: Deprecated IRootDataObjectFactory ([#18565](https://github.com/microsoft/FluidFramework/issues/18565)) [030ab7adf9](https://github.com/microsoft/FluidFramework/commits/030ab7adf991d2d983437544600a191ac15ca5a5)
 
-    The `IRootDataObjectFactory` interface has been deprecated and will be removed in a future major release. Please remove
-    all usage of it.
+  The `IRootDataObjectFactory` interface has been deprecated and will be removed in a future major release. Please remove
+  all usage of it.
 
 ## 2.0.0-internal.7.3.0
 
@@ -250,97 +254,97 @@ Dependency updates only.
 
 ### Major Changes
 
--   aqueduct: ContainerRuntimeFactory constructors have changed [871b3493dd](https://github.com/microsoft/FluidFramework/commits/871b3493dd0d7ea3a89be64998ceb6cb9021a04e)
+- aqueduct: ContainerRuntimeFactory constructors have changed [871b3493dd](https://github.com/microsoft/FluidFramework/commits/871b3493dd0d7ea3a89be64998ceb6cb9021a04e)
 
-    The following class constructors have been changed to allow for better flexible in arguments passed:
+  The following class constructors have been changed to allow for better flexible in arguments passed:
 
-    -   `BaseContainerRuntimeFactory`
-    -   `ContainerRuntimeFactoryWithDefaultDataStore`
-    -   `RuntimeFactory`
+  - `BaseContainerRuntimeFactory`
+  - `ContainerRuntimeFactoryWithDefaultDataStore`
+  - `RuntimeFactory`
 
-    They now use a single object for constructor params. Example change to be made:
+  They now use a single object for constructor params. Example change to be made:
 
-    ```ts
-    // Old
-    new BaseContainerRuntimeFactory(
-    	myRegistryEntries,
-    	myDependencyContainer,
-    	myRequestHandlers,
-    	myRuntimeOptions,
-    	myProvideEntryPoint,
-    );
+  ```ts
+  // Old
+  new BaseContainerRuntimeFactory(
+    myRegistryEntries,
+    myDependencyContainer,
+    myRequestHandlers,
+    myRuntimeOptions,
+    myProvideEntryPoint,
+  );
 
-    // New
-    new BaseContainerRuntimeFactory({
-    	registryEntries: myRegistryEntries,
-    	dependencyContainer: myDependencyContainer,
-    	requestHandlers: myRequestHandlers,
-    	runtimeOptions: myRuntimeOptions,
-    	provideEntryPoint: myProvideEntryPoint,
-    });
-    ```
+  // New
+  new BaseContainerRuntimeFactory({
+    registryEntries: myRegistryEntries,
+    dependencyContainer: myDependencyContainer,
+    requestHandlers: myRequestHandlers,
+    runtimeOptions: myRuntimeOptions,
+    provideEntryPoint: myProvideEntryPoint,
+  });
+  ```
 
--   DEPRECATED: container-runtime: requestHandlers are deprecated [871b3493dd](https://github.com/microsoft/FluidFramework/commits/871b3493dd0d7ea3a89be64998ceb6cb9021a04e)
+- DEPRECATED: container-runtime: requestHandlers are deprecated [871b3493dd](https://github.com/microsoft/FluidFramework/commits/871b3493dd0d7ea3a89be64998ceb6cb9021a04e)
 
-    The concept of `requestHandlers` has been deprecated. Please migrate all usage of the following APIs to the new `entryPoint` pattern:
+  The concept of `requestHandlers` has been deprecated. Please migrate all usage of the following APIs to the new `entryPoint` pattern:
 
-    -   `requestHandler` property in `ContainerRuntime.loadRuntime(...)`
-    -   `RuntimeRequestHandler`
-    -   `RuntimeRequestHandlerBuilder`
-    -   `defaultFluidObjectRequestHandler(...)`
-    -   `defaultRouteRequestHandler(...)`
-    -   `mountableViewRequestHandler(...)`
-    -   `buildRuntimeRequestHandler(...)`
-    -   `createFluidObjectResponse(...)`
-    -   `handleFromLegacyUri(...)`
-    -   `rootDataStoreRequestHandler(...)`
+  - `requestHandler` property in `ContainerRuntime.loadRuntime(...)`
+  - `RuntimeRequestHandler`
+  - `RuntimeRequestHandlerBuilder`
+  - `defaultFluidObjectRequestHandler(...)`
+  - `defaultRouteRequestHandler(...)`
+  - `mountableViewRequestHandler(...)`
+  - `buildRuntimeRequestHandler(...)`
+  - `createFluidObjectResponse(...)`
+  - `handleFromLegacyUri(...)`
+  - `rootDataStoreRequestHandler(...)`
 
-    See [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md) for more details.
+  See [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md) for more details.
 
--   DEPRECATED: container-loader: Various request related APIs have been deprecated [871b3493dd](https://github.com/microsoft/FluidFramework/commits/871b3493dd0d7ea3a89be64998ceb6cb9021a04e)
+- DEPRECATED: container-loader: Various request related APIs have been deprecated [871b3493dd](https://github.com/microsoft/FluidFramework/commits/871b3493dd0d7ea3a89be64998ceb6cb9021a04e)
 
-    Please remove all calls to the following functions and instead use the new `entryPoint` pattern:
+  Please remove all calls to the following functions and instead use the new `entryPoint` pattern:
 
-    -   `requestFluidObject`
-    -   `requestResolvedObjectFromContainer`
-    -   `getDefaultObjectFromContainer`
-    -   `getObjectWithIdFromContainer`
-    -   `getObjectFromContainer`
+  - `requestFluidObject`
+  - `requestResolvedObjectFromContainer`
+  - `getDefaultObjectFromContainer`
+  - `getObjectWithIdFromContainer`
+  - `getObjectFromContainer`
 
-    See [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md) for more details.
+  See [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md) for more details.
 
--   container-definitions: IContainer's and IDataStore's IFluidRouter capabilities are deprecated [871b3493dd](https://github.com/microsoft/FluidFramework/commits/871b3493dd0d7ea3a89be64998ceb6cb9021a04e)
+- container-definitions: IContainer's and IDataStore's IFluidRouter capabilities are deprecated [871b3493dd](https://github.com/microsoft/FluidFramework/commits/871b3493dd0d7ea3a89be64998ceb6cb9021a04e)
 
-    `IFluidRouter` and `request({ url: "/" })` on `IContainer` and `IDataStore` are deprecated and will be removed in a future major release. Please migrate all usage to the appropriate `getEntryPoint()` or `entryPoint` APIs.
+  `IFluidRouter` and `request({ url: "/" })` on `IContainer` and `IDataStore` are deprecated and will be removed in a future major release. Please migrate all usage to the appropriate `getEntryPoint()` or `entryPoint` APIs.
 
-    See [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md) for more details.
+  See [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md) for more details.
 
--   test-utils: provideEntryPoint is required [871b3493dd](https://github.com/microsoft/FluidFramework/commits/871b3493dd0d7ea3a89be64998ceb6cb9021a04e)
+- test-utils: provideEntryPoint is required [871b3493dd](https://github.com/microsoft/FluidFramework/commits/871b3493dd0d7ea3a89be64998ceb6cb9021a04e)
 
-    The optional `provideEntryPoint` method has become required on a number of constructors. A value will need to be provided to the following classes:
+  The optional `provideEntryPoint` method has become required on a number of constructors. A value will need to be provided to the following classes:
 
-    -   `BaseContainerRuntimeFactory`
-    -   `RuntimeFactory`
-    -   `ContainerRuntime` (constructor and `loadRuntime`)
-    -   `FluidDataStoreRuntime`
+  - `BaseContainerRuntimeFactory`
+  - `RuntimeFactory`
+  - `ContainerRuntime` (constructor and `loadRuntime`)
+  - `FluidDataStoreRuntime`
 
-    See [testContainerRuntimeFactoryWithDefaultDataStore.ts](https://github.com/microsoft/FluidFramework/tree/main/packages/test/test-utils/src/testContainerRuntimeFactoryWithDefaultDataStore.ts) for an example implemtation of `provideEntryPoint` for ContainerRuntime.
-    See [pureDataObjectFactory.ts](https://github.com/microsoft/FluidFramework/tree/main/packages/framework/aqueduct/src/data-object-factories/pureDataObjectFactory.ts#L83) for an example implementation of `provideEntryPoint` for DataStoreRuntime.
+  See [testContainerRuntimeFactoryWithDefaultDataStore.ts](https://github.com/microsoft/FluidFramework/tree/main/packages/test/test-utils/src/testContainerRuntimeFactoryWithDefaultDataStore.ts) for an example implemtation of `provideEntryPoint` for ContainerRuntime.
+  See [pureDataObjectFactory.ts](https://github.com/microsoft/FluidFramework/tree/main/packages/framework/aqueduct/src/data-object-factories/pureDataObjectFactory.ts#L83) for an example implementation of `provideEntryPoint` for DataStoreRuntime.
 
-    Subsequently, various `entryPoint` and `getEntryPoint()` endpoints have become required. Please see [containerRuntime.ts](https://github.com/microsoft/FluidFramework/tree/main/packages/runtime/container-runtime/src/containerRuntime.ts) for example implementations of these APIs.
+  Subsequently, various `entryPoint` and `getEntryPoint()` endpoints have become required. Please see [containerRuntime.ts](https://github.com/microsoft/FluidFramework/tree/main/packages/runtime/container-runtime/src/containerRuntime.ts) for example implementations of these APIs.
 
-    For more details, see [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md)
+  For more details, see [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md)
 
--   Minimum TypeScript version now 5.1.6 [871b3493dd](https://github.com/microsoft/FluidFramework/commits/871b3493dd0d7ea3a89be64998ceb6cb9021a04e)
+- Minimum TypeScript version now 5.1.6 [871b3493dd](https://github.com/microsoft/FluidFramework/commits/871b3493dd0d7ea3a89be64998ceb6cb9021a04e)
 
-    The minimum supported TypeScript version for Fluid 2.0 clients is now 5.1.6.
+  The minimum supported TypeScript version for Fluid 2.0 clients is now 5.1.6.
 
--   aqueduct: EventForwarder and IDisposable members removed from PureDataObject [871b3493dd](https://github.com/microsoft/FluidFramework/commits/871b3493dd0d7ea3a89be64998ceb6cb9021a04e)
+- aqueduct: EventForwarder and IDisposable members removed from PureDataObject [871b3493dd](https://github.com/microsoft/FluidFramework/commits/871b3493dd0d7ea3a89be64998ceb6cb9021a04e)
 
-    The `EventForwarder` and `IDisposable` members of `PureDataObject` were deprecated in 2.0.0-internal.5.2.0 and have now been removed.
+  The `EventForwarder` and `IDisposable` members of `PureDataObject` were deprecated in 2.0.0-internal.5.2.0 and have now been removed.
 
-    If your code was overriding any methods/properties from `EventForwarder` and or `IDisposable` on a class that inherits
-    (directly or transitively) from `PureDataObject`, you'll have to remove the `override` keyword.
+  If your code was overriding any methods/properties from `EventForwarder` and or `IDisposable` on a class that inherits
+  (directly or transitively) from `PureDataObject`, you'll have to remove the `override` keyword.
 
 ## 2.0.0-internal.6.4.0
 
@@ -354,43 +358,43 @@ Dependency updates only.
 
 ### Minor Changes
 
--   PureDataObject temporarily extends EventForwarder and implements IDisposable again ([#16846](https://github.com/microsoft/FluidFramework/issues/16846)) [9825a692dd](https://github.com/microsoft/FluidFramework/commits/9825a692dd27eded214e3978a7fd6028b05e6fab)
-
-    `PureDataObject` extends `EventForwarder` and implements `IDìsposable` again to ease the transition to `2.0.0-internal.6.x`.
-    These interfaces will no longer be implemented on `PureDataObject` in version `2.0.0-internal.7.0.0`.
-
-    The original deprecation announcement for these members can be found [here](https://github.com/microsoft/FluidFramework/releases/tag/client_v2.0.0-internal.5.2.0).
-
-    Once the change is re-applied in `2.0.0-internal.7.0.0`, if your code was overriding any methods/properties from
-    `EventForwarder` and or `IDisposable` on a class that inherits (directly or transitively) from `PureDataObject`,
-    you'll have to remove the `override` keyword.
-
--   Remove use of @fluidframework/common-definitions ([#16638](https://github.com/microsoft/FluidFramework/issues/16638)) [a8c81509c9](https://github.com/microsoft/FluidFramework/commits/a8c81509c9bf09cfb2092ebcf7265205f9eb6dbf)
-
-    The **@fluidframework/common-definitions** package is being deprecated, so the following interfaces and types are now
-    imported from the **@fluidframework/core-interfaces** package:
-
-    -   interface IDisposable
-    -   interface IErrorEvent
-    -   interface IErrorEvent
-    -   interface IEvent
-    -   interface IEventProvider
-    -   interface ILoggingError
-    -   interface ITaggedTelemetryPropertyType
-    -   interface ITelemetryBaseEvent
-    -   interface ITelemetryBaseLogger
-    -   interface ITelemetryErrorEvent
-    -   interface ITelemetryGenericEvent
-    -   interface ITelemetryLogger
-    -   interface ITelemetryPerformanceEvent
-    -   interface ITelemetryProperties
-    -   type ExtendEventProvider
-    -   type IEventThisPlaceHolder
-    -   type IEventTransformer
-    -   type ReplaceIEventThisPlaceHolder
-    -   type ReplaceIEventThisPlaceHolder
-    -   type TelemetryEventCategory
-    -   type TelemetryEventPropertyType
+- PureDataObject temporarily extends EventForwarder and implements IDisposable again ([#16846](https://github.com/microsoft/FluidFramework/issues/16846)) [9825a692dd](https://github.com/microsoft/FluidFramework/commits/9825a692dd27eded214e3978a7fd6028b05e6fab)
+
+  `PureDataObject` extends `EventForwarder` and implements `IDìsposable` again to ease the transition to `2.0.0-internal.6.x`.
+  These interfaces will no longer be implemented on `PureDataObject` in version `2.0.0-internal.7.0.0`.
+
+  The original deprecation announcement for these members can be found [here](https://github.com/microsoft/FluidFramework/releases/tag/client_v2.0.0-internal.5.2.0).
+
+  Once the change is re-applied in `2.0.0-internal.7.0.0`, if your code was overriding any methods/properties from
+  `EventForwarder` and or `IDisposable` on a class that inherits (directly or transitively) from `PureDataObject`,
+  you'll have to remove the `override` keyword.
+
+- Remove use of @fluidframework/common-definitions ([#16638](https://github.com/microsoft/FluidFramework/issues/16638)) [a8c81509c9](https://github.com/microsoft/FluidFramework/commits/a8c81509c9bf09cfb2092ebcf7265205f9eb6dbf)
+
+  The **@fluidframework/common-definitions** package is being deprecated, so the following interfaces and types are now
+  imported from the **@fluidframework/core-interfaces** package:
+
+  - interface IDisposable
+  - interface IErrorEvent
+  - interface IErrorEvent
+  - interface IEvent
+  - interface IEventProvider
+  - interface ILoggingError
+  - interface ITaggedTelemetryPropertyType
+  - interface ITelemetryBaseEvent
+  - interface ITelemetryBaseLogger
+  - interface ITelemetryErrorEvent
+  - interface ITelemetryGenericEvent
+  - interface ITelemetryLogger
+  - interface ITelemetryPerformanceEvent
+  - interface ITelemetryProperties
+  - type ExtendEventProvider
+  - type IEventThisPlaceHolder
+  - type IEventTransformer
+  - type ReplaceIEventThisPlaceHolder
+  - type ReplaceIEventThisPlaceHolder
+  - type TelemetryEventCategory
+  - type TelemetryEventPropertyType
 
 ## 2.0.0-internal.6.1.0
 
@@ -400,27 +404,27 @@ Dependency updates only.
 
 ### Major Changes
 
--   `initializeEntryPoint` will become required [8abce8cdb4](https://github.com/microsoft/FluidFramework/commits/8abce8cdb4e2832fb6405fb44e393bef03d5648a)
+- `initializeEntryPoint` will become required [8abce8cdb4](https://github.com/microsoft/FluidFramework/commits/8abce8cdb4e2832fb6405fb44e393bef03d5648a)
 
-    The optional `initializeEntryPoint` method has been added to a number of constructors. **This method argument will become required in an upcoming release** and a value will need to be provided to the following classes:
+  The optional `initializeEntryPoint` method has been added to a number of constructors. **This method argument will become required in an upcoming release** and a value will need to be provided to the following classes:
 
-    -   `BaseContainerRuntimeFactory`
-    -   `ContainerRuntimeFactoryWithDefaultDataStore`
-    -   `RuntimeFactory`
-    -   `ContainerRuntime` (constructor and `loadRuntime`)
-    -   `FluidDataStoreRuntime`
+  - `BaseContainerRuntimeFactory`
+  - `ContainerRuntimeFactoryWithDefaultDataStore`
+  - `RuntimeFactory`
+  - `ContainerRuntime` (constructor and `loadRuntime`)
+  - `FluidDataStoreRuntime`
 
-    For an example implementation of `initializeEntryPoint`, see [pureDataObjectFactory.ts](https://github.com/microsoft/FluidFramework/blob/main/packages/framework/aqueduct/src/data-object-factories/pureDataObjectFactory.ts#L84).
+  For an example implementation of `initializeEntryPoint`, see [pureDataObjectFactory.ts](https://github.com/microsoft/FluidFramework/blob/main/packages/framework/aqueduct/src/data-object-factories/pureDataObjectFactory.ts#L84).
 
-    This work will replace the request pattern. See [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md) for more info on this effort.
+  This work will replace the request pattern. See [Removing-IFluidRouter.md](https://github.com/microsoft/FluidFramework/blob/main/packages/common/core-interfaces/Removing-IFluidRouter.md) for more info on this effort.
 
--   EventForwarder and IDisposable members removed from PureDataObject [8abce8cdb4](https://github.com/microsoft/FluidFramework/commits/8abce8cdb4e2832fb6405fb44e393bef03d5648a)
+- EventForwarder and IDisposable members removed from PureDataObject [8abce8cdb4](https://github.com/microsoft/FluidFramework/commits/8abce8cdb4e2832fb6405fb44e393bef03d5648a)
 
-    The EventForwarder and IDisposable members of PureDataObject were deprecated in 2.0.0-internal.5.2.0 and have now been removed.
+  The EventForwarder and IDisposable members of PureDataObject were deprecated in 2.0.0-internal.5.2.0 and have now been removed.
 
--   Upgraded typescript transpilation target to ES2020 [8abce8cdb4](https://github.com/microsoft/FluidFramework/commits/8abce8cdb4e2832fb6405fb44e393bef03d5648a)
+- Upgraded typescript transpilation target to ES2020 [8abce8cdb4](https://github.com/microsoft/FluidFramework/commits/8abce8cdb4e2832fb6405fb44e393bef03d5648a)
 
-    Upgraded typescript transpilation target to ES2020. This is done in order to decrease the bundle sizes of Fluid Framework packages. This has provided size improvements across the board for ex. Loader, Driver, Runtime etc. Reduced bundle sizes helps to load lesser code in apps and hence also helps to improve the perf.If any app wants to target any older versions of browsers with which this target version is not compatible, then they can use packages like babel to transpile to a older target.
+  Upgraded typescript transpilation target to ES2020. This is done in order to decrease the bundle sizes of Fluid Framework packages. This has provided size improvements across the board for ex. Loader, Driver, Runtime etc. Reduced bundle sizes helps to load lesser code in apps and hence also helps to improve the perf.If any app wants to target any older versions of browsers with which this target version is not compatible, then they can use packages like babel to transpile to a older target.
 
 ## 2.0.0-internal.5.4.0
 
@@ -434,9 +438,9 @@ Dependency updates only.
 
 ### Minor Changes
 
--   EventForwarder and IDisposable members deprecated from PureDataObject ([#16201](https://github.com/microsoft/FluidFramework/issues/16201)) [0e838fdb3e](https://github.com/microsoft/FluidFramework/commits/0e838fdb3e8187481f41c4116a67458c2a1658d5)
+- EventForwarder and IDisposable members deprecated from PureDataObject ([#16201](https://github.com/microsoft/FluidFramework/issues/16201)) [0e838fdb3e](https://github.com/microsoft/FluidFramework/commits/0e838fdb3e8187481f41c4116a67458c2a1658d5)
 
-    The EventForwarder and IDisposable members have been deprecated from PureDataObject and will be removed in an upcoming release. The EventForwarder pattern was mostly unused by the current implementation, and is also recommended against generally (instead, register and forward events explicitly). The disposal implementation was incomplete and likely to cause poor behavior as the disposal was not observable by default. Inheritors of the PureDataObject can of course still implement their own disposal logic.
+  The EventForwarder and IDisposable members have been deprecated from PureDataObject and will be removed in an upcoming release. The EventForwarder pattern was mostly unused by the current implementation, and is also recommended against generally (instead, register and forward events explicitly). The disposal implementation was incomplete and likely to cause poor behavior as the disposal was not observable by default. Inheritors of the PureDataObject can of course still implement their own disposal logic.
 
 ## 2.0.0-internal.5.1.0
 
@@ -446,17 +450,17 @@ Dependency updates only.
 
 ### Major Changes
 
--   The following functions and classes were deprecated in previous releases and have been removed: [8b242fdc79](https://github.com/microsoft/FluidFramework/commits/8b242fdc796714cf1da9ad3f90d02efb122af0c2)
+- The following functions and classes were deprecated in previous releases and have been removed: [8b242fdc79](https://github.com/microsoft/FluidFramework/commits/8b242fdc796714cf1da9ad3f90d02efb122af0c2)
 
-    -   `PureDataObject.getFluidObjectFromDirectory`
-    -   `IProvideContainerRuntime` and its `IContainerRuntime` member.
-    -   `ContainerRuntime`'s `IProvideContainerRuntime` has also been removed.
+  - `PureDataObject.getFluidObjectFromDirectory`
+  - `IProvideContainerRuntime` and its `IContainerRuntime` member.
+  - `ContainerRuntime`'s `IProvideContainerRuntime` has also been removed.
 
 ## 2.0.0-internal.4.4.0
 
 ### Minor Changes
 
--   `PureDataObject.getFluidObjectFromDirectory` has been deprecated and will be removed in an upcoming release. Instead prefer to interface directly with the directory and handles. [9238304c77](https://github.com/microsoft/FluidFramework/commits/9238304c772d447225f6f86417033ca8004c0edd)
+- `PureDataObject.getFluidObjectFromDirectory` has been deprecated and will be removed in an upcoming release. Instead prefer to interface directly with the directory and handles. [9238304c77](https://github.com/microsoft/FluidFramework/commits/9238304c772d447225f6f86417033ca8004c0edd)
 
 ## 2.0.0-internal.4.1.0