deps(dev): bump aegir from 40.0.13 to 41.0.0 (#27)

Bumps [aegir](https://github.com/ipfs/aegir) from 40.0.13 to 41.0.0.
- [Release notes](https://github.com/ipfs/aegir/releases)
- [Changelog](https://github.com/ipfs/aegir/blob/master/CHANGELOG.md)
- [Commits](ipfs/aegir@v40.0.13...v41.0.0)

---
updated-dependencies:
- dependency-name: aegir
  dependency-type: direct:development
  update-type: version-update:semver-major
...

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: achingbrain <[email protected]>

Author: dependabot[bot]

README.md

@@ -9,20 +9,14 @@
 
 ## Table of contents <!-- omit in toc -->
 
-- [About](#about)
 - [Install](#install)
   - [Browser `<script>` tag](#browser-script-tag)
+- [About](#about)
 - [Example](#example)
 - [API Docs](#api-docs)
 - [License](#license)
 - [Contribution](#contribution)
 
-## About
-
-This is an implementation of the libp2p [content routing interface](https://libp2p.github.io/js-libp2p-interfaces/interfaces/_libp2p_interface_content_routing.ContentRouting.html) that uses an [IPNI](https://github.com/ipni/specs) HTTP endpoint.
-
-An alternative is [HTTP Routing V1](https://github.com/libp2p/js-reframe-content-routing) (previously known as Reframe) but the advantage of IPNI at least as of 2023-05-19 is that it returns results in a streaming fashion which can be faster.  Note that this will change with the rollout of [IPIP-410](https://github.com/ipfs/specs/pull/410), at which point one can use the HTTP Routing V1 interface/implementation directly.
-
 ## Install
 
 ```console
@@ -37,6 +31,12 @@ Loading this module through a script tag will make it's exports available as `Li
 <script src="https://unpkg.com/@libp2p/ipni-content-routing/dist/index.min.js"></script>
 ```
 
+## About
+
+This is an implementation of the libp2p [content routing interface](https://libp2p.github.io/js-libp2p-interfaces/interfaces/_libp2p_interface_content_routing.ContentRouting.html) that uses an [IPNI](https://github.com/ipni/specs) HTTP endpoint.
+
+An alternative is [HTTP Routing V1](https://github.com/libp2p/js-reframe-content-routing) (previously known as Reframe) but the advantage of IPNI at least as of 2023-05-19 is that it returns results in a streaming fashion which can be faster.  Note that this will change with the rollout of [IPIP-410](https://github.com/ipfs/specs/pull/410), at which point one can use the HTTP Routing V1 interface/implementation directly.
+
 ## Example
 
 ```js

package.json

@@ -11,10 +11,6 @@
   "bugs": {
     "url": "https://github.com/libp2p/js-ipni-content-routing/issues"
   },
-  "engines": {
-    "node": ">=16.0.0",
-    "npm": ">=7.0.0"
-  },
   "type": "module",
   "types": "./dist/src/index.d.ts",
   "files": [
@@ -32,6 +28,7 @@
   "eslintConfig": {
     "extends": "ipfs",
     "parserOptions": {
+      "project": true,
       "sourceType": "module"
     }
   },
@@ -149,7 +146,7 @@
   },
   "devDependencies": {
     "@libp2p/peer-id-factory": "^3.0.2",
-    "aegir": "^40.0.8",
+    "aegir": "^41.0.0",
     "body-parser": "^1.20.2",
     "it-all": "^3.0.1"
   }

typedoc.json

@@ -0,0 +1,5 @@
+{
+  "entryPoints": [
+    "./src/index.ts"
+  ]
+}