arangojs 10.0.0-alpha.1 → 10.0.0

package/CHANGELOG.md

@@ -14,97 +14,105 @@ This driver uses semantic versioning:
 - A change in the major version (e.g. 1.Y.Z -> 2.0.0) indicates _breaking_
   changes that require changes in your code to upgrade.
 
-## [10.0.0-alpha.1] - 2024-12-09
+## [10.0.0] - 2025-01-06
 
 This is a major release and breaks backwards compatibility.
 
 See [the migration guide](./MIGRATING.md#v9-to-v10) for detailed instructions
 for upgrading your code to arangojs v10.
 
-### Changed
-
-- Renamed `CollectionDropOptions` type to `DropCollectionOptions`
-
-- Renamed `CollectionTruncateOptions` type to `TruncateCollectionOptions`
-
-- Renamed `Config` type to `ConfigOptions`
-
-- Renamed `path` option to `pathname` in `RequestOptions` type
+### Removed
 
-  This affects the `db.waitForPropagation` and `route.request` methods.
+- Removed unused `CreateUserOptions` type
 
-- Removed `basePath` option from `RequestOptions` type
+  The actual type used by the `db.createUser` method is still `UserOptions`.
 
-  This affects the `db.waitForPropagation` and `route.request` methods.
+- Removed unused `IndexDetails` type
 
-- Renamed `route.path` property to `route.pathname`
+  This type was intended to be returned by `collection.indexes` when the
+  `withStats` option is set to `true` but the `figures` property is already
+  included in the current return type.
 
-- Changed error type constructor signatures
+- Removed Node.js 18 support
 
-  The `request` property is now always positional and the `options` property
-  is always optional.
+  Node.js 18 will reach its end of life in May 2025, so arangojs will no
+  longer support this version of Node.js going forward.
 
-- Moved configuration related types to new `config` module
+  For more information, see [the Node.js release schedule](https://nodejs.dev/en/about/releases/).
 
-  The following types were moved: `Config`, `LoadBalancingStrategy`,
-  `BasicAuthCredentials` and `BearerAuthCredentials`.
+### Changed
 
-- Moved `ArangoErrorResponse` type to `connection` module
+- Closing a connection now closes all open requests
 
-  The type is now also no longer marked as internal.
+  Previously in certain situations only the most recent request would be
+  closed per server. Note that this still merely aborts the requests but
+  does not guarantee the underlying connections are closed as these are
+  handled by Node.js or the browser natively. need to be installed
+  otherwise.
 
-- Moved configuration related types to new `configuration` module
+- Moved fetch-specific `config` options from into `config.fetchOptions`
 
-  The following types were moved: `ConfigOptions`, `LoadBalancingStrategy`,
-  `BasicAuthCredentials` and `BearerAuthCredentials`.
+  The following options were moved: `credentials`, `headers` and `keepalive`.
 
-- Moved internal utility functions to new `lib/util` module
+- `db.setUserAccessLevel` now takes `grant` as a separate parameter
 
-  These methods are all still marked as internal and should not be used
-  directly.
+  The parameter was previously passed as an additional property in the
+  `options` parameter.
 
-- Closing a connection now closes all open requests
+#### Error handling
 
-  Previously in certain situations only the most recent request would be
-  closed per server. Note that this still merely aborts the requests but
-  does not guarantee the underlying connections are closed as these are
-  handled by Node.js or the browser natively.
+- Errors encountered before a request completes are now wrapped in a
+  `NetworkError` or a subclass thereof
 
-### Added
+  This should help making it easier to diagnose network issues and distinguish
+  the relevant error conditions.
 
-- Restored support for Unix domain sockets
+  The originating error can still be accessed using the `cause` property of the
+  `NetworkError` error.
 
-  Using Unix domain sockets requires the `undici` library to be installed.
+- `HttpError` now extends the `NetworkError` class
 
-- Restored support for `config.agentOptions`
+  This allows treating all non-`ArangoError` errors as one category of errors,
+  even when there is no server response available.
 
-  The `config.agentOptions` option can now be used to create a custom `undici`
-  agent if the `undici` library is installed.
+- `db.waitForPropagation` now throws a `PropagationTimeoutError` error when
+  invoked with a `timeout` option and the timeout duration is exceeded
 
-## [10.0.0-alpha.0] - 2024-11-28
+  The method would previously throw the most recent error encountered while
+  waiting for replication. The originating error can still be accessed using
+  the `cause` property of the `PropagationTimeoutError` error.
 
-This is a major release and breaks backwards compatibility.
+- `db.waitForPropagation` now respects the `timeout` option more strictly
 
-See [the migration guide](./MIGRATING.md#v9-to-v10) for detailed instructions
-for upgrading your code to arangojs v10.
+  Previously the method would only time out if the timeout duration was
+  exceeded after the most recent request failed. Now the timeout is
+  recalculated and passed on to each request, preventing it from exceeding
+  the specified duration.
 
-### Removed
+  If the propagation timed out due to an underlying request exceeding the
+  timeout duration, the `cause` property of the `PropagationTimeoutError`
+  error will be a `ResponseTimeoutError` error.
 
-- Removed unused `CreateUserOptions` type
+- `config.beforeRequest` and `config.afterResponse` callbacks can now return
+  promises
 
-  The actual type used by the `db.createUser` method is still `UserOptions`.
+  If the callback returns a promise, it will be awaited before the request
+  and response cycle proceeds. If either callback throws an error or returns
+  a promise that is rejected, that error will be thrown instead.
 
-- Removed unused `IndexDetails` type
+- `config.afterResponse` callback signature changed
 
-  This type was intended to be returned by `collection.indexes` when the
-  `withStats` option is set to `true` but the `figures` property is already
-  included in the current return type.
+  The callback signature previously used the internal `ArangojsResponse` type.
+  The new signature uses the `Response` type of the Fetch API with an
+  additional `request` property to more accurately represent the actual value
+  it receives as the `parsedBody` property will never be present.
 
-### Changed
+- `response` property on `ArangoError` is now optional
 
-- Changed `QueueTimeMetrics` type to an interface
+  This property should always be present but this allows using the error in
+  situations where a response might not be available.
 
-- Changed `CursorExtras` and `CursorStats` interfaces to types
+#### General type changes
 
 - Changed `GraphVertexCollection` and `GraphEdgeCollection` generic types to
   take separate `EntryResultType` and `EntryInputType` type parameters
@@ -115,13 +123,43 @@ for upgrading your code to arangojs v10.
 
   These type parameters are used to narrow the the returned collection type.
 
-- Renamed `db.listServiceScripts` method to `db.getServiceScripts`
-- Renamed `db.listHotBackups` method to `db.getHotBackups`
-- Renamed `db.getLogMessages` method to `db.listLogMessages`
-- Renamed `db.listFunctions` method to `db.listUserFunctions`
-- Renamed `db.createFunction` method to `db.createUserFunction`
-- Renamed `db.dropFunction` method to `db.dropUserFunction`
-- Changed `db.removeUser` method to return `void`
+- Changed `db.removeUser` method return type to `Promise<void>`
+
+  The previous return type served no purpose.
+
+- Changed `QueueTimeMetrics` type to an interface
+
+- Changed `CursorExtras` and `CursorStats` interfaces to types
+
+#### Low-level request/route changes
+
+- Renamed `path` option to `pathname` in `RequestOptions` type
+
+  This affects the `db.waitForPropagation` and `route.request` methods.
+
+- Removed `basePath` option from `RequestOptions` type
+
+  This affects the `db.waitForPropagation` and `route.request` methods.
+
+- Renamed `route.path` property to `route.pathname`
+
+#### Renamed methods
+
+- Renamed various methods for consistency:
+
+  Methods that return an array now follow the `listNouns` pattern, methods that
+  return a "list of nouns" wrapped in an object have been renamed to follow the
+  `getNouns` pattern to avoid confusion:
+
+  - `db.listServiceScripts` -> `db.getServiceScripts`
+  - `db.listHotBackups` -> `db.getHotBackups`
+  - `db.listFunctions` -> `db.listUserFunctions`
+  - `db.getLogMessages` -> `db.listLogMessages`
+
+- Renamed AQL user function management methods:
+
+  - `db.createFunction` -> `db.createUserFunction`
+  - `db.dropFunction` -> `db.dropUserFunction`
 
 #### Module renaming
 
@@ -140,13 +178,18 @@ for upgrading your code to arangojs v10.
   - `arangojs/transaction` -> `arangojs/transactions`
   - `arangojs/view` -> `arangojs/views`
 
+- Moved internal utility functions to new `arangojs/lib/util` module
+
+  These methods are all still marked as internal and should not be used
+  directly.
+
 #### Moved types
 
 - Moved document related types from `arangojs/collection` module to
   `arangojs/documents` module
 
   The following types were moved: `DocumentOperationFailure`,
-  `DocumentOperationMetadata`, `DocumentExistsOptions`, 
+  `DocumentOperationMetadata`, `DocumentExistsOptions`,
   `CollectionReadOptions`, `CollectionBatchReadOptions`,
   `CollectionInsertOptions`, `CollectionReplaceOptions`,
   `CollectionUpdateOptions`, `CollectionRemoveOptions`,
@@ -182,7 +225,8 @@ for upgrading your code to arangojs v10.
 
   The following types were moved: `QueryOptions`, `ExplainOptions`,
   `ExplainPlan`, `ExplainStats`, `SingleExplainResult`, `MultiExplainResult`,
-  `AstNode`, `ParseResult`, `QueryOptimizerRule`, `QueryTracking`,
+  `AstNode`, `ParseResult`, `QueryCachePropertiesOptions`, `QueryCacheEntry`,
+  `QueryCacheProperties`, `QueryOptimizerRule`, `QueryTracking`,
   `QueryTrackingOptions`, `QueryInfo` and `AqlUserFunction`.
 
 - Moved service related types from `arangojs/database` module to new
@@ -206,7 +250,24 @@ for upgrading your code to arangojs v10.
 - Moved server administration related types from `arangojs/database` module to
   new `arangojs/administration` module
 
-  The following types were moved: `QueueTimeMetrics` and `VersionInfo`.
+  The following types were moved: `CompactOptions`, `EngineInfo`,
+  `EngineStatsInfo`, `LicenseInfo`, `QueueTimeMetrics`, `ServerAvailability`,
+  `ServerStatusInformation`, `SingleServerSupportInfo`, `ClusterSupportInfo`
+  and `VersionInfo`.
+
+- Moved configuration related types to new `arangojs/config` module
+
+  The following types were moved: `Config`, `LoadBalancingStrategy`,
+  `BasicAuthCredentials` and `BearerAuthCredentials`.
+
+- Moved `ArangoErrorResponse` type to `arangojs/connection` module
+
+  The type is now also no longer marked as internal.
+
+- Moved configuration related types to new `arangojs/configuration` module
+
+  The following types were moved: `ConfigOptions`, `LoadBalancingStrategy`,
+  `BasicAuthCredentials` and `BearerAuthCredentials`.
 
 #### Renamed types
 
@@ -218,8 +279,11 @@ for upgrading your code to arangojs v10.
   - `GeoIndex` -> `GeoIndexDescription`
   - `PersistentIndex` -> `PersistentIndexDescription`
   - `PrimaryIndex` -> `PrimaryIndexDescription`
+  - `EdgeIndex` -> `EdgeIndexDescription`
   - `TtlIndex` -> `TtlIndexDescription`
+  - `FulltextIndex` -> `FulltextIndexDescription`
   - `MdiIndex` -> `MdiIndexDescription`
+  - `MdiPrefixedIndex` -> `MdiPrefixedIndexDescription`
   - `InvertedIndex` -> `InvertedIndexDescription`
   - `InternalArangosearchIndex` -> `ArangosearchIndexDescription`
   - `InternalIndex` -> `InternalIndexDescription`
@@ -231,21 +295,43 @@ for upgrading your code to arangojs v10.
 
 - Renamed various types for consistency:
 
+  Types representing an instance of a specific entity type in ArangoDB like a
+  collection, graph or query now follow the `NounDescription` naming pattern:
+
   - `AqlUserFunction` -> `UserFunctionDescription`
   - `CollectionMetadata` -> `CollectionDescription`
   - `DatabaseInfo` -> `DatabaseDescription`
   - `GraphInfo` -> `GraphDescription`
   - `ServiceInfo` -> `ServiceDescription`
   - `QueryInfo` -> `QueryDescription`
+  - `TransactionDetails` -> `TransactionDescription`
+
+  Note that the `TransactionDescription` type used by `db.listTransactions`
+  is slightly different from the `TransactionInfo` type used by methods of
+  `Transaction` objects due to implementation details of ArangoDB.
+
+  Types representing general information rather than an instance of something
+  now generally follow the `NounInfo` naming pattern, whereas types
+  representing the result of an operation generally follow the `NounResult`
+  or `VerbNounResult` naming pattern:
+
   - `QueryTracking` -> `QueryTrackingInfo`
-  - `TransactionDetails` -> `TransactionInfo`
+  - `ServerStatusInformation` -> `ServerStatusInfo`
+  - `CollectionImportResult` -> `ImportDocumentsResult`
+  - `CollectionEdgesResult` -> `DocumentEdgesResult`
+
+  Types for options passed to methods now generally follow the `NounOptions`,
+  `VerbNounOptions` or `VerbNounAttributeOptions` naming patterns:
+
+  - `Config` -> `ConfigOptions`
   - `TransactionCollections` -> `TransactionCollectionOptions`
   - `CreateDatabaseUser` -> `CreateDatabaseUserOptions`
-
-  - Index operations:
-    - `IndexListOptions` -> `ListIndexesOptions`
+  - `CollectionDropOptions` -> `DropCollectionOptions`
+  - `CollectionTruncateOptions` -> `TruncateCollectionOptions`
+  - `IndexListOptions` -> `ListIndexesOptions`
 
   - Collection document operations:
+
     - `DocumentExistsOptions` -> `DocumentExistsOptions`
     - `CollectionReadOptions` -> `ReadDocumentOptions`
     - `CollectionBatchReadOptions` -> `BulkReadDocumentsOptions`
@@ -255,10 +341,9 @@ for upgrading your code to arangojs v10.
     - `CollectionRemoveOptions` -> `RemoveDocumentOptions`
     - `CollectionImportOptions` -> `ImportDocumentsOptions`
     - `CollectionEdgesOptions` -> `DocumentEdgesOptions`
-    - `CollectionImportResult` -> `ImportDocumentsResult`
-    - `CollectionEdgesResult` -> `DocumentEdgesResult`
 
   - Graph collection document operation:
+
     - `GraphCollectionReadOptions` -> `ReadGraphDocumentOptions`
     - `GraphCollectionInsertOptions` -> `CreateGraphDocumentOptions`
     - `GraphCollectionReplaceOptions` -> `ReplaceGraphDocumentOptions`
@@ -266,6 +351,7 @@ for upgrading your code to arangojs v10.
     - `ViewPatchPropertiesOptions` -> `UpdateViewPropertiesOptions`
 
   - View operations:
+
     - `ArangoSearchViewPatchPropertiesOptions` -> `UpdateArangoSearchViewPropertiesOptions`
     - `SearchAliasViewPatchPropertiesOptions` -> `UpdateSearchAliasViewPropertiesOptions`
     - `SearchAliasViewPatchIndexOptions` -> `UpdateSearchAliasViewIndexOptions`
@@ -284,67 +370,41 @@ for upgrading your code to arangojs v10.
   - `ObjectWithId` (in `documents` module) -> `ObjectWithDocumentId`
   - `ObjectWithKey` (in `documents` module) -> `ObjectWithDocumentKey`
 
-#### Error handling
-
-- Errors encountered before a request completes are now wrapped in a
-  `NetworkError` or a subclass thereof
-
-  This should help making it easier to diagnose network issues and distinguish
-  the relevant error conditions.
-
-  The originating error can still be accessed using the `cause` property of the
-  `NetworkError` error.
-
-- `HttpError` now extends the `NetworkError` class
-
-  This allows treating all non-`ArangoError` errors as one category of errors,
-  even when there is no server response available.
-
-- `db.waitForPropagation` now throws a `PropagationTimeoutError` error when
-  invoked with a `timeout` option and the timeout duration is exceeded
+### Added
 
-  The method would previously throw the most recent error encountered while
-  waiting for replication. The originating error can still be accessed using
-  the `cause` property of the `PropagationTimeoutError` error.
+- Restored support for Unix domain sockets
 
-- `db.waitForPropagation` now respects the `timeout` option more strictly
+  Using Unix domain sockets requires the `undici` library to be installed.
 
-  Previously the method would only time out if the timeout duration was
-  exceeded after the most recent request failed. Now the timeout is
-  recalculated and passed on to each request, preventing it from exceeding
-  the specified duration.
+- Restored support for `config.agentOptions`
 
-  If the propagation timed out due to an underlying request exceeding the
-  timeout duration, the `cause` property of the `PropagationTimeoutError`
-  error will be a `ResponseTimeoutError` error.
+  The `config.agentOptions` option can now be used to create a custom `undici`
+  agent if the `undici` library is installed.
 
-- `config.beforeRequest` and `config.afterResponse` callbacks can now return
-  promises
+- Added `config.fetchOptions` option
 
-  If the callback returns a promise, it will be awaited before the request
-  and response cycle proceeds. If either callback throws an error or returns
-  a promise that is rejected, that error will be thrown instead.
+  This option can now be used to specify default options for the `fetch`
+  function used by arangojs like `headers`, `credentials`, `keepalive` and
+  `redirect`.
 
-- `config.afterResponse` callback signature changed
+- Added `BatchCursor#itemsView` property and `BatchCursorItemsView` interface
 
-  The callback signature previously used the internal `ArangojsResponse` type.
-  The new signature uses the `Response` type of the Fetch API with an
-  additional `request` property to more accurately represent the actual value
-  it receives as the `parsedBody` property will never be present.
+  This property provides a low-level interface for consuming the items of the
+  cursor and is used by the regular item-wise `Cursor` class internally.
 
-- `response` property on `ArangoError` is now optional
+- Added `SystemIndexDescription` type
 
-  This property should always be present but this allows using the error in
-  situations where a response might not be available.
+  This type represents either of the system index types `primary` and `edge`
+  and can be used to cast indexes returned by `collection.indexes`.
 
-### Added
+- Added `ProcessedResponse` type
 
-- Added `BatchCursor#itemsView` property and `BatchCursorItemsView` interface
+  This type replaces the previously internal `ArangojsResponse` type and
+  extends the native `Response` type with additional properties.
 
-  This property provides a low-level interface for consuming the items of the
-  cursor and is used by the regular item-wise `Cursor` class internally.
+#### Error handling
 
-- Added `onError` option to `Config` (DE-955)
+- Added `config.onError` option (DE-955)
 
   This option can be used to specify a callback function that will be invoked
   whenever a request results in an error. Unlike `afterResponse`, this callback
@@ -355,6 +415,22 @@ for upgrading your code to arangojs v10.
   If the `onError` callback throws an error or returns a promise that is
   rejected, that error will be thrown instead.
 
+- Added support for `config.fetchOptions.redirect` option ([#613](https://github.com/arangodb/arangojs/issues/613))
+
+  This option can now be used to specify the redirect mode for requests.
+
+  When set to `"manual"`, arangojs will throw an `HttpError` wrapping the
+  redirect response instead of automatically following redirects.
+
+  Note that when set to `"error"`, the native fetch API will throw a
+  non-specific error (usually a `TypeError`) that arangojs will wrap in a
+  `FetchFailedError` instead.
+
+- Added optional `ArangoError#request` property
+
+  This property is always present if the error has a `response` property. In
+  normal use this should always be the case.
+
 - Added `NetworkError` class
 
   This is the common base class for all errors (including `HttpError`) that
@@ -395,27 +471,48 @@ for upgrading your code to arangojs v10.
   `cause` property. This error is only thrown when `db.waitForPropagation`
   is invoked with a `timeout` option and the timeout duration is exceeded.
 
-- Added `ProcessedResponse` type
+## [9.3.0] - 2025-01-06
 
-  This type replaces the previously internal `ArangojsResponse` type and
-  extends the native `Response` type with additional properties.
+### Added
 
-- Added optional `ArangoError#request` property
+- Added `db.compact` method (DE-906)
 
-  This property is always present if the error has a `response` property. In
-  normal use this should always be the case.
+- Added `db.engineStats` method (DE-932)
+
+- Added `db.getLicense` and `db.setLicense` methods (DE-949)
+
+- Added `db.listQueryCacheEntries` method (DE-149)
+
+- Added `db.clearQueryCache` method (DE-148)
+
+- Added `db.getQueryCacheProperties` method (DE-150)
+
+- Added `db.setQueryCacheProperties` method (DE-151)
+
+- Added `collection.shards` method (DE-939)
+
+- Added support for `mdi-prefixed` indexes (DE-956)
+
+- Restored `fulltext` index type support (DE-957)
+
+  The `fulltext` index type is still no longer supported for creating new
+  indexes but can be used to cast existing indexes from `Index`.
+
+- Added support for `edge` indexes (DE-958)
+
+  The `Index` type now can also be cast to the `EdgeIndex` type.
 
 ## [9.2.0] - 2024-11-27
 
 ### Added
 
-- Added `database.availability` method
+- Added `db.availability` method
 
-- Added `database.engine` method (DE-931)
+- Added `db.engine` method (DE-931)
 
-- Added `database.status` method ([#811](https://github.com/arangodb/arangojs/issues/811))
+- Added `db.status` method ([#811](https://github.com/arangodb/arangojs/issues/811))
 
-- Added `database.supportInfo` method
+- Added `db.supportInfo` method
 
 - Added `keepNull` option to `CollectionInsertOptions` type (DE-946)
 
@@ -1510,7 +1607,7 @@ For a detailed list of changes between pre-release versions of v7 see the
 
 - Changed `db.createDatabase` return type to `Database`
 
-- Renamed `database.setQueryTracking` to `database.queryTracking`
+- Renamed `db.setQueryTracking` to `db.queryTracking`
 
   The method will now return the existing query tracking properties or set the
   new query tracking properties depending on whether an argument is provided.
@@ -1906,7 +2003,7 @@ For a detailed list of changes between pre-release versions of v7 see the
 
 - Added support for ArangoDB 3.5 Analyzers API
 
-  See the documentation of the `database.analyzer` method and the `Analyzer`
+  See the documentation of the `db.analyzer` method and the `Analyzer`
   instances for information on using this API.
 
 - Added `collection.getResponsibleShard` method
@@ -2080,7 +2177,7 @@ For a detailed list of changes between pre-release versions of v7 see the
 
 - Fixed `edgeCollection.save` not respecting options ([#554](https://github.com/arangodb/arangojs/issues/554))
 
-- Fixed `database.createDatabase` TypeScript signature ([#561](https://github.com/arangodb/arangojs/issues/561))
+- Fixed `db.createDatabase` TypeScript signature ([#561](https://github.com/arangodb/arangojs/issues/561))
 
 ## [6.5.0] - 2018-08-03
 
@@ -2121,7 +2218,7 @@ For a detailed list of changes between pre-release versions of v7 see the
 
 - Added `ArangoError` and `CollectionType` to public exports
 
-- Added `database.close` method
+- Added `db.close` method
 
 - Added `opts` parameter to `EdgeCollection#save`
 
@@ -2129,11 +2226,11 @@ For a detailed list of changes between pre-release versions of v7 see the
 
 ### Added
 
-- Added `database.version` method
+- Added `db.version` method
 
-- Added `database.login` method
+- Added `db.login` method
 
-- Added `database.exists` method
+- Added `db.exists` method
 
 - Added `collection.exists` method
 
@@ -2355,8 +2452,8 @@ For a detailed list of changes between pre-release versions of v7 see the
 
   Graph methods now only return the relevant part of the response body.
 
-[10.0.0-alpha.1]: https://github.com/arangodb/arangojs/compare/v10.0.0-alpha.0...v10.0.0-alpha.1
-[10.0.0-alpha.0]: https://github.com/arangodb/arangojs/compare/v9.2.0...v10.0.0-alpha.0
+[10.0.0]: https://github.com/arangodb/arangojs/compare/v9.3.0...v10.0.0
+[9.3.0]: https://github.com/arangodb/arangojs/compare/v9.2.0...v9.3.0
 [9.2.0]: https://github.com/arangodb/arangojs/compare/v9.1.0...v9.2.0
 [9.1.0]: https://github.com/arangodb/arangojs/compare/v9.0.0...v9.1.0
 [9.0.0]: https://github.com/arangodb/arangojs/compare/v8.8.1...v9.0.0

package/README.md

@@ -36,7 +36,7 @@ You can also use [jsDelivr CDN](https://www.jsdelivr.com) during development:
 <script type="importmap">
   {
     "imports": {
-      "arangojs": "https://cdn.jsdelivr.net/npm/arangojs@9.0.0/esm/index.js?+esm"
+      "arangojs": "https://cdn.jsdelivr.net/npm/arangojs@10.0.0/esm/index.js?+esm"
     }
   }
 </script>
@@ -183,7 +183,7 @@ For more details on the errors thrown by `undici`, see the
 Please make sure you are using the latest version of this driver and that the
 version of the arangojs documentation you are reading matches that version.
 
-Changes in the major version number of arangojs (e.g. 8.x.y -> 9.0.0) indicate
+Changes in the major version number of arangojs (e.g. 9.x.y -> 10.0.0) indicate
 backwards-incompatible changes in the arangojs API that may require changes in
 your code when upgrading your version of arangojs.
 
@@ -194,10 +194,10 @@ the [compatibility section](#compatibility) for additional information.
 You can install an older version of arangojs using `npm` or `yarn`:
 
 ```sh
-# for version 8.x.x
-yarn add arangojs@8
+# for version 9.x.x
+yarn add arangojs@9
 # - or -
-npm install --save arangojs@8
+npm install --save arangojs@9
 ```
 
 ### No code intelligence when using require instead of import
@@ -272,7 +272,7 @@ available.
 ### Unix domain sockets
 
 If you want to use Unix domain sockets, you need to install the `undici` module,
-which is an optional dependency of arangojs.
+which is an optional peer dependency of arangojs.
 
 ```sh
 npm install --save undici
@@ -285,7 +285,8 @@ message indicating that the `undici` module is unavailable.
 ### Node.js with self-signed HTTPS certificates
 
 If you need to support self-signed HTTPS certificates in Node.js, you will need
-to install the `undici` module, which is an optional dependency of arangojs.
+to install the `undici` module, which is an optional peer dependency of
+arangojs.
 
 ```sh
 npm install --save undici