@hot-updater/plugin-api-keys 1.0.0-rc.42 → 1.0.0-rc.44

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.
Files changed (2) hide show
  1. package/README.md +9 -3
  2. package/package.json +3 -3
package/README.md CHANGED
@@ -4,11 +4,17 @@ Hot Updater's API keys plugin. It protects the server's client routes with API
4
4
  keys and stores their SHA-256 digests; the built-in `hot-updater api-key`
5
5
  manages them.
6
6
 
7
- You don't install it on its own. `@hot-updater/server` depends on it and
8
- re-exports its `./server` entry:
7
+ You don't install it on its own. In `hot-updater.config.ts`, use the CLI's
8
+ plugin entry:
9
9
 
10
10
  ```ts
11
- import { apiKeys } from "@hot-updater/server/plugins/api-keys";
11
+ import { apiKeys } from "hot-updater/plugins";
12
+ ```
13
+
14
+ In a `createHotUpdater` server definition, use the server's entry:
15
+
16
+ ```ts
17
+ import { apiKeys } from "@hot-updater/server/plugins";
12
18
  ```
13
19
 
14
20
  See [API key authentication](https://hot-updater.dev/docs/custom/api-key-authentication).
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@hot-updater/plugin-api-keys",
3
3
  "type": "module",
4
- "version": "1.0.0-rc.42",
4
+ "version": "1.0.0-rc.44",
5
5
  "description": "Hot Updater's API keys plugin: protects client routes with API keys and manages them",
6
6
  "exports": {
7
7
  "./server": {
@@ -30,10 +30,10 @@
30
30
  "devDependencies": {
31
31
  "@types/node": "^20",
32
32
  "vitest": "4.1.4",
33
- "@hot-updater/plugin-core": "1.0.0-rc.42"
33
+ "@hot-updater/plugin-core": "1.0.0-rc.44"
34
34
  },
35
35
  "peerDependencies": {
36
- "@hot-updater/plugin-core": "^1.0.0-rc.42"
36
+ "@hot-updater/plugin-core": "^1.0.0-rc.44"
37
37
  },
38
38
  "scripts": {
39
39
  "build": "tsdown",