@prosopo/cli 3.7.22 → 3.7.24

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.
@@ -1,5 +1,5 @@
1
1
 
2
- > @prosopo/cli@3.7.22 build:cjs
2
+ > @prosopo/cli@3.7.24 build:cjs
3
3
  > NODE_ENV=${NODE_ENV:-development}; vite build --config vite.cjs.config.ts --mode $NODE_ENV
4
4
 
5
5
  ViteCommonJSConfig: .
@@ -78,7 +78,7 @@ dist/cjs/cli.cjs 1.76 kB │ gzip: 0.64 kB
78
78
  dist/cjs/reloader.cjs 1.87 kB │ gzip: 0.76 kB
79
79
  dist/cjs/commands/migrateAbuserScoreThreshold.cjs 2.17 kB │ gzip: 0.90 kB
80
80
  dist/cjs/argv.cjs 2.30 kB │ gzip: 0.66 kB
81
- dist/cjs/start.cjs 2.75 kB │ gzip: 0.85 kB
81
+ dist/cjs/start.cjs 2.34 kB │ gzip: 0.80 kB
82
82
  dist/cjs/commands/siteKeyRegisterApi.cjs 3.08 kB │ gzip: 1.08 kB
83
83
  dist/cjs/commands/siteKeyRegister.cjs 3.48 kB │ gzip: 1.15 kB
84
84
  dist/cjs/prosopo.config.cjs 4.58 kB │ gzip: 1.46 kB
@@ -92,4 +92,4 @@ dist/cjs/RateLimiter.cjs 5.58 kB │ gzip: 0.89 kB
92
92
   │ ╰─────── This `import.meta` will be replaced with an empty object (`{}`) automatically. If this is desired, you can suppress this warning by adding `transform.define: { 'import.meta': {} }`. If `import.meta` needs to be kept as-is, you need to set the output format to `esm`.
93
93
  ────╯
94
94
  
95
- ✓ built in 61ms
95
+ ✓ built in 56ms
@@ -1,8 +1,8 @@
1
1
 
2
- > @prosopo/cli@3.7.22 build:tsc
2
+ > @prosopo/cli@3.7.24 build:tsc
3
3
  > tsc --build --verbose
4
4
 
5
- 8:35:50 PM - Projects in this build:
5
+ 10:11:04 PM - Projects in this build:
6
6
  * ../../dev/config/tsconfig.json
7
7
  * ../locale/tsconfig.json
8
8
  * ../util/tsconfig.json
@@ -29,55 +29,55 @@
29
29
  * ../../dev/workspace/tsconfig.json
30
30
  * tsconfig.json
31
31
 
32
- 8:35:50 PM - Project '../../dev/config/tsconfig.json' is up to date because newest input '../../dev/config/src/webpack/webpack.config.ts' is older than output '../../dev/config/tsconfig.tsbuildinfo'
32
+ 10:11:04 PM - Project '../../dev/config/tsconfig.json' is up to date because newest input '../../dev/config/src/webpack/webpack.config.ts' is older than output '../../dev/config/tsconfig.tsbuildinfo'
33
33
 
34
- 8:35:50 PM - Project '../locale/tsconfig.json' is up to date because newest input '../locale/src/translationKey.ts' is older than output '../locale/tsconfig.tsbuildinfo'
34
+ 10:11:04 PM - Project '../locale/tsconfig.json' is up to date because newest input '../locale/src/translationKey.ts' is older than output '../locale/tsconfig.tsbuildinfo'
35
35
 
36
- 8:35:50 PM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/url.ts' is older than output '../util/tsconfig.tsbuildinfo'
36
+ 10:11:04 PM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/url.ts' is older than output '../util/tsconfig.tsbuildinfo'
37
37
 
38
- 8:35:50 PM - Project '../util-crypto/tsconfig.json' is up to date because newest input '../util-crypto/src/types.ts' is older than output '../util-crypto/tsconfig.tsbuildinfo'
38
+ 10:11:04 PM - Project '../util-crypto/tsconfig.json' is up to date because newest input '../util-crypto/src/types.ts' is older than output '../util-crypto/tsconfig.tsbuildinfo'
39
39
 
40
- 8:35:50 PM - Project '../types/tsconfig.json' is up to date because newest input '../types/src/types.test-d.ts' is older than output '../types/tsconfig.tsbuildinfo'
40
+ 10:11:04 PM - Project '../types/tsconfig.json' is up to date because newest input '../types/src/types.test-d.ts' is older than output '../types/tsconfig.tsbuildinfo'
41
41
 
42
- 8:35:50 PM - Project '../api/tsconfig.json' is up to date because newest input '../api/src/index.ts' is older than output '../api/tsconfig.tsbuildinfo'
42
+ 10:11:04 PM - Project '../api/tsconfig.json' is up to date because newest input '../api/src/index.ts' is older than output '../api/tsconfig.tsbuildinfo'
43
43
 
44
- 8:35:50 PM - Project '../logger/tsconfig.json' is up to date because newest input '../logger/src/index.ts' is older than output '../logger/tsconfig.tsbuildinfo'
44
+ 10:11:04 PM - Project '../logger/tsconfig.json' is up to date because newest input '../logger/src/index.ts' is older than output '../logger/tsconfig.tsbuildinfo'
45
45
 
46
- 8:35:50 PM - Project '../common/tsconfig.json' is up to date because newest input '../common/src/error.ts' is older than output '../common/tsconfig.tsbuildinfo'
46
+ 10:11:04 PM - Project '../common/tsconfig.json' is up to date because newest input '../common/src/error.ts' is older than output '../common/tsconfig.tsbuildinfo'
47
47
 
48
- 8:35:50 PM - Project '../dotenv/tsconfig.json' is up to date because newest input '../dotenv/src/env.ts' is older than output '../dotenv/tsconfig.tsbuildinfo'
48
+ 10:11:04 PM - Project '../dotenv/tsconfig.json' is up to date because newest input '../dotenv/src/index.ts' is older than output '../dotenv/tsconfig.tsbuildinfo'
49
49
 
50
- 8:35:50 PM - Project '../ipinfo/tsconfig.json' is up to date because newest input '../ipinfo/src/index.ts' is older than output '../ipinfo/tsconfig.tsbuildinfo'
50
+ 10:11:04 PM - Project '../ipinfo/tsconfig.json' is up to date because newest input '../ipinfo/src/IpInfoService.ts' is older than output '../ipinfo/tsconfig.tsbuildinfo'
51
51
 
52
- 8:35:50 PM - Project '../api-route/tsconfig.json' is up to date because newest input '../api-route/src/apiRoutes.ts' is older than output '../api-route/tsconfig.tsbuildinfo'
52
+ 10:11:04 PM - Project '../api-route/tsconfig.json' is up to date because newest input '../api-route/src/apiRoutes.ts' is older than output '../api-route/tsconfig.tsbuildinfo'
53
53
 
54
- 8:35:50 PM - Project '../redis-client/tsconfig.json' is up to date because newest input '../redis-client/src/index.ts' is older than output '../redis-client/tsconfig.tsbuildinfo'
54
+ 10:11:04 PM - Project '../redis-client/tsconfig.json' is up to date because newest input '../redis-client/src/index.ts' is older than output '../redis-client/tsconfig.tsbuildinfo'
55
55
 
56
- 8:35:50 PM - Project '../user-access-policy/tsconfig.json' is up to date because newest input '../user-access-policy/src/transformRule.ts' is older than output '../user-access-policy/tsconfig.tsbuildinfo'
56
+ 10:11:04 PM - Project '../user-access-policy/tsconfig.json' is up to date because newest input '../user-access-policy/src/transformRule.ts' is older than output '../user-access-policy/tsconfig.tsbuildinfo'
57
57
 
58
- 8:35:50 PM - Project '../types-database/tsconfig.json' is up to date because newest input '../types-database/src/index.ts' is older than output '../types-database/tsconfig.tsbuildinfo'
58
+ 10:11:04 PM - Project '../types-database/tsconfig.json' is up to date because newest input '../types-database/src/types.test-d.ts' is older than output '../types-database/tsconfig.tsbuildinfo'
59
59
 
60
- 8:35:50 PM - Project '../database/tsconfig.json' is up to date because newest input '../database/src/tests/unit/redisCacheEscalation.unit.test.ts' is older than output '../database/tsconfig.tsbuildinfo'
60
+ 10:11:04 PM - Project '../database/tsconfig.json' is up to date because newest input '../database/src/tests/mongoGlobalSetup.ts' is older than output '../database/tsconfig.tsbuildinfo'
61
61
 
62
- 8:35:50 PM - Project '../keyring/tsconfig.json' is up to date because newest input '../keyring/src/index.ts' is older than output '../keyring/tsconfig.tsbuildinfo'
62
+ 10:11:04 PM - Project '../keyring/tsconfig.json' is up to date because newest input '../keyring/src/keyring/keyring.test.ts' is older than output '../keyring/tsconfig.tsbuildinfo'
63
63
 
64
- 8:35:50 PM - Project '../types-env/tsconfig.json' is up to date because newest input '../types-env/src/env.ts' is older than output '../types-env/tsconfig.tsbuildinfo'
64
+ 10:11:04 PM - Project '../types-env/tsconfig.json' is up to date because newest input '../types-env/src/env.ts' is older than output '../types-env/tsconfig.tsbuildinfo'
65
65
 
66
- 8:35:50 PM - Project '../env/tsconfig.json' is up to date because newest input '../env/src/env.ts' is older than output '../env/tsconfig.tsbuildinfo'
66
+ 10:11:04 PM - Project '../env/tsconfig.json' is up to date because newest input '../env/src/env.ts' is older than output '../env/tsconfig.tsbuildinfo'
67
67
 
68
- 8:35:51 PM - Project '../api-express-router/tsconfig.json' is up to date because newest input '../api-express-router/src/middlewares/requestLoggerMiddleware.ts' is older than output '../api-express-router/tsconfig.tsbuildinfo'
68
+ 10:11:04 PM - Project '../api-express-router/tsconfig.json' is up to date because newest input '../api-express-router/src/middlewares/requestLoggerMiddleware.ts' is older than output '../api-express-router/tsconfig.tsbuildinfo'
69
69
 
70
- 8:35:51 PM - Project '../datasets/tsconfig.json' is up to date because newest input '../datasets/src/tests/dataset.unit.test.ts' is older than output '../datasets/tsconfig.tsbuildinfo'
70
+ 10:11:04 PM - Project '../datasets/tsconfig.json' is up to date because newest input '../datasets/src/tests/dataset.unit.test.ts' is older than output '../datasets/tsconfig.tsbuildinfo'
71
71
 
72
- 8:35:51 PM - Project '../load-balancer/tsconfig.json' is up to date because newest input '../load-balancer/src/balancer.ts' is older than output '../load-balancer/tsconfig.tsbuildinfo'
72
+ 10:11:04 PM - Project '../load-balancer/tsconfig.json' is up to date because newest input '../load-balancer/src/index.ts' is older than output '../load-balancer/tsconfig.tsbuildinfo'
73
73
 
74
- 8:35:51 PM - Project '../puzzle-assets/tsconfig.json' is up to date because newest input '../puzzle-assets/src/background.ts' is older than output '../puzzle-assets/tsconfig.tsbuildinfo'
74
+ 10:11:04 PM - Project '../puzzle-assets/tsconfig.json' is up to date because newest input '../puzzle-assets/src/background.ts' is older than output '../puzzle-assets/tsconfig.tsbuildinfo'
75
75
 
76
- 8:35:51 PM - Project '../provider/tsconfig.json' is up to date because newest input '../provider/src/utils/normalizeRequestIp.ts' is older than output '../provider/tsconfig.tsbuildinfo'
76
+ 10:11:04 PM - Project '../provider/tsconfig.json' is up to date because newest input '../provider/src/util.ts' is older than output '../provider/tsconfig.tsbuildinfo'
77
77
 
78
- 8:35:51 PM - Project '../../dev/workspace/tsconfig.json' is up to date because newest input '../../dev/workspace/src/index.ts' is older than output '../../dev/workspace/tsconfig.tsbuildinfo'
78
+ 10:11:04 PM - Project '../../dev/workspace/tsconfig.json' is up to date because newest input '../../dev/workspace/src/index.ts' is older than output '../../dev/workspace/tsconfig.tsbuildinfo'
79
79
 
80
- 8:35:51 PM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
80
+ 10:11:04 PM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
81
81
 
82
- 8:35:51 PM - Building project '/home/runner/work/captcha/captcha/packages/cli/tsconfig.json'...
82
+ 10:11:04 PM - Building project '/home/runner/work/captcha/captcha/packages/cli/tsconfig.json'...
83
83
 
@@ -1,9 +1,9 @@
1
1
 
2
- > @prosopo/cli@3.7.22 build
2
+ > @prosopo/cli@3.7.24 build
3
3
  > npm run build:cross-env -- --mode ${NODE_ENV:-development}
4
4
 
5
5
 
6
- > @prosopo/cli@3.7.22 build:cross-env
6
+ > @prosopo/cli@3.7.24 build:cross-env
7
7
  > vite build --config vite.esm.config.ts --mode production
8
8
 
9
9
  ViteEsmConfig: .
@@ -34,6 +34,7 @@ ViteEsmConfig: .
34
34
  ]
35
35
  }
36
36
  {
37
+ The plugin "vite-tsconfig-paths" is detected. Vite now supports tsconfig paths resolution natively via the resolve.tsconfigPaths option. You can remove the plugin and set resolve.tsconfigPaths: true in your Vite config instead.
37
38
  externals: [
38
39
  '@prosopo/api',
39
40
  '@prosopo/types',
@@ -59,7 +60,6 @@ ViteEsmConfig: .
59
60
  '@prosopo/puzzle-assets'
60
61
  ]
61
62
  }
62
- The plugin "vite-tsconfig-paths" is detected. Vite now supports tsconfig paths resolution natively via the resolve.tsconfigPaths option. You can remove the plugin and set resolve.tsconfigPaths: true in your Vite config instead.
63
63
  vite v8.1.5 building ssr environment for production...
64
64
  Bundle build started
65
65
  
@@ -81,11 +81,11 @@ dist/cli.js 1.34 kB │ gzip: 0.55 kB
81
81
  dist/commands/updateSpamEmailDomains.js 1.53 kB │ gzip: 0.64 kB
82
82
  dist/reloader.js 1.62 kB │ gzip: 0.69 kB
83
83
  dist/argv.js 1.98 kB │ gzip: 0.59 kB
84
+ dist/start.js 2.11 kB │ gzip: 0.78 kB
84
85
  dist/commands/migrateAbuserScoreThreshold.js 2.11 kB │ gzip: 0.89 kB
85
- dist/start.js 2.49 kB │ gzip: 0.82 kB
86
86
  dist/commands/siteKeyRegisterApi.js 2.97 kB │ gzip: 1.06 kB
87
87
  dist/commands/siteKeyRegister.js 3.30 kB │ gzip: 1.14 kB
88
88
  dist/prosopo.config.js 4.43 kB │ gzip: 1.47 kB
89
89
  dist/RateLimiter.js 5.16 kB │ gzip: 0.89 kB
90
90
 
91
- ✓ built in 56ms
91
+ ✓ built in 61ms
package/CHANGELOG.md CHANGED
@@ -1,5 +1,37 @@
1
1
  # @prosopo/cli
2
2
 
3
+ ## 3.7.24
4
+ ### Patch Changes
5
+
6
+ - 68a9b41: chore(deps): bump the npm-minor-and-patch group across 1 directory with 36 updates
7
+ - f850d07: chore(deps): bump body-parser and express
8
+ - Updated dependencies [68a9b41]
9
+ - Updated dependencies [f850d07]
10
+ - Updated dependencies [ce5a3d7]
11
+ - Updated dependencies [4cd6b04]
12
+ - @prosopo/locale@3.3.1
13
+ - @prosopo/provider@5.3.10
14
+ - @prosopo/types@5.2.6
15
+ - @prosopo/util@3.3.7
16
+ - @prosopo/env@3.6.41
17
+ - @prosopo/api@4.0.14
18
+ - @prosopo/common@3.1.51
19
+ - @prosopo/dotenv@3.0.53
20
+ - @prosopo/keyring@2.9.77
21
+ - @prosopo/logger@2.0.7
22
+
23
+ ## 3.7.23
24
+ ### Patch Changes
25
+
26
+ - dfc1fa6: Two provider-DB latency fixes.
27
+
28
+ **Pin the pending-stage sweep to its compound partial index.** `getUnstoredDappUserCommitments`, `getUnstoredDappUserPoWCommitments`, and `getUnstoredSessionRecords` now call `.hint("pendingStage_partial")`. Observed post-index-fix on 2026-08-21: mongo's planner sometimes picked plain `IXSCAN {_id:1}` over the compound `{pendingStage:1, _id:1}` for `find({pendingStage:true}).sort({_id:1})`, scanning the whole collection and filtering in memory until the 30s socket timeout killed the connection. Clearing the plan cache re-planned once but didn't prevent recurrence after future catalog changes — the hint makes the choice explicit and permanent.
29
+
30
+ **Remove local context-entropy computation.** Deletes `sampleContextEntropy` (the `$sample`-then-`$lookup` aggregation), `setClientContextEntropy`, `ClientTaskManager.calculateClientEntropy`, and the `setClientEntropy` scheduler + CLI registration. Was accounting for ~36 minutes of DB time every 6h against `powcaptchas` and `sessions` — the `$lookup` fanned out to 10 000 session reads per invocation to produce 75 sampled sessionIds. Same computation now runs off-provider in the external job-runner across the full record set; the provider keeps `getClientContextEntropy` for the DM's read path (the job-runner writes to the same `clientcontextentropies` collection).
31
+ - Updated dependencies [dfc1fa6]
32
+ - @prosopo/provider@5.3.9
33
+ - @prosopo/env@3.6.40
34
+
3
35
  ## 3.7.22
4
36
  ### Patch Changes
5
37
 
@@ -3457,9 +3457,12 @@ var s = () => !!(typeof window < "u" && window.document && window.document.creat
3457
3457
  {
3458
3458
  key: "write",
3459
3459
  value: function() {
3460
- for (var e in this.queuedWrites) {
3461
- var t = this.queuedWrites[e];
3462
- if (e !== "locks") for (var n in t) this.writeFile(e, n);
3460
+ for (var e = 0, t = Object.keys(this.queuedWrites); e < t.length; e++) {
3461
+ var n = t[e], r = this.queuedWrites[n];
3462
+ if (n !== "locks") for (var i = 0, a = Object.keys(r); i < a.length; i++) {
3463
+ var o = a[i];
3464
+ this.writeFile(n, o);
3465
+ }
3463
3466
  }
3464
3467
  }
3465
3468
  },