@prosopo/cli 3.7.12 → 3.7.14

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 (7) hide show
  1. package/.turbo/turbo-build$colon$cjs.log +6 -4
  2. package/.turbo/turbo-build$colon$tsc.log +30 -27
  3. package/.turbo/turbo-build.log +7 -5
  4. package/CHANGELOG.md +17 -0
  5. package/Dockerfile +9 -6
  6. package/dist/bundle/provider.cli.bundle.js +11313 -11005
  7. package/package.json +6 -6
package/.turbo/turbo-build$colon$cjs.log CHANGED
@@ -1,5 +1,5 @@
1
1
 
2
- > @prosopo/cli@3.7.12 build:cjs
2
+ > @prosopo/cli@3.7.14 build:cjs
3
3
  > NODE_ENV=${NODE_ENV:-development}; vite build --config vite.cjs.config.ts --mode $NODE_ENV
4
4
 
5
5
  ViteCommonJSConfig: .
@@ -25,7 +25,8 @@ ViteCommonJSConfig: .
25
25
  '/home/runner/work/captcha/captcha/packages/provider/tsconfig.json',
26
26
  '/home/runner/work/captcha/captcha/packages/api-express-router/tsconfig.json',
27
27
  '/home/runner/work/captcha/captcha/packages/datasets/tsconfig.json',
28
- '/home/runner/work/captcha/captcha/packages/load-balancer/tsconfig.json'
28
+ '/home/runner/work/captcha/captcha/packages/load-balancer/tsconfig.json',
29
+ '/home/runner/work/captcha/captcha/packages/puzzle-assets/tsconfig.json'
29
30
  ]
30
31
  }
31
32
  {
@@ -50,7 +51,8 @@ ViteCommonJSConfig: .
50
51
  '@prosopo/provider',
51
52
  '@prosopo/api-express-router',
52
53
  '@prosopo/datasets',
53
- '@prosopo/load-balancer'
54
+ '@prosopo/load-balancer',
55
+ '@prosopo/puzzle-assets'
54
56
  ]
55
57
  }
56
58
  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.
@@ -90,4 +92,4 @@ dist/cjs/RateLimiter.cjs 5.58 kB │ gzip: 0.89 kB
90
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`.
91
93
  ────╯
92
94
  
93
- ✓ built in 44ms
95
+ ✓ built in 80ms
package/.turbo/turbo-build$colon$tsc.log CHANGED
@@ -1,8 +1,8 @@
1
1
 
2
- > @prosopo/cli@3.7.12 build:tsc
2
+ > @prosopo/cli@3.7.14 build:tsc
3
3
  > tsc --build --verbose
4
4
 
5
- 11:34:30 AM - Projects in this build:
5
+ 1:39:26 PM - Projects in this build:
6
6
  * ../../dev/config/tsconfig.json
7
7
  * ../locale/tsconfig.json
8
8
  * ../util/tsconfig.json
@@ -24,57 +24,60 @@
24
24
  * ../api-express-router/tsconfig.json
25
25
  * ../datasets/tsconfig.json
26
26
  * ../load-balancer/tsconfig.json
27
+ * ../puzzle-assets/tsconfig.json
27
28
  * ../provider/tsconfig.json
28
29
  * ../../dev/workspace/tsconfig.json
29
30
  * tsconfig.json
30
31
 
31
- 11:34:30 AM - Project '../../dev/config/tsconfig.json' is up to date because newest input '../../dev/config/src/vite/NodejsPolarsNativeFilePlugin.ts' is older than output '../../dev/config/tsconfig.tsbuildinfo'
32
+ 1:39:26 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
33
 
33
- 11:34:30 AM - Project '../locale/tsconfig.json' is up to date because newest input '../locale/src/translationKey.ts' is older than output '../locale/tsconfig.tsbuildinfo'
34
+ 1:39:26 PM - Project '../locale/tsconfig.json' is up to date because newest input '../locale/src/translationKey.ts' is older than output '../locale/tsconfig.tsbuildinfo'
34
35
 
35
- 11:34:30 AM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/url.ts' is older than output '../util/tsconfig.tsbuildinfo'
36
+ 1:39:26 PM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/verifyRecency.ts' is older than output '../util/tsconfig.tsbuildinfo'
36
37
 
37
- 11:34:30 AM - 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
+ 1:39:26 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
39
 
39
- 11:34:30 AM - 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
+ 1:39:26 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
41
 
41
- 11:34:30 AM - Project '../api/tsconfig.json' is up to date because newest input '../api/src/index.ts' is older than output '../api/tsconfig.tsbuildinfo'
42
+ 1:39:26 PM - Project '../api/tsconfig.json' is up to date because newest input '../api/src/index.ts' is older than output '../api/tsconfig.tsbuildinfo'
42
43
 
43
- 11:34:30 AM - Project '../logger/tsconfig.json' is up to date because newest input '../logger/src/index.ts' is older than output '../logger/tsconfig.tsbuildinfo'
44
+ 1:39:26 PM - Project '../logger/tsconfig.json' is up to date because newest input '../logger/src/index.ts' is older than output '../logger/tsconfig.tsbuildinfo'
44
45
 
45
- 11:34:30 AM - Project '../common/tsconfig.json' is up to date because newest input '../common/src/error.ts' is older than output '../common/tsconfig.tsbuildinfo'
46
+ 1:39:26 PM - Project '../common/tsconfig.json' is up to date because newest input '../common/src/index.ts' is older than output '../common/tsconfig.tsbuildinfo'
46
47
 
47
- 11:34:30 AM - Project '../dotenv/tsconfig.json' is up to date because newest input '../dotenv/src/env.ts' is older than output '../dotenv/tsconfig.tsbuildinfo'
48
+ 1:39:26 PM - Project '../dotenv/tsconfig.json' is up to date because newest input '../dotenv/src/env.ts' is older than output '../dotenv/tsconfig.tsbuildinfo'
48
49
 
49
- 11:34:30 AM - Project '../ipinfo/tsconfig.json' is up to date because newest input '../ipinfo/src/types.ts' is older than output '../ipinfo/tsconfig.tsbuildinfo'
50
+ 1:39:26 PM - Project '../ipinfo/tsconfig.json' is up to date because newest input '../ipinfo/src/IpInfoService.ts' is older than output '../ipinfo/tsconfig.tsbuildinfo'
50
51
 
51
- 11:34:30 AM - 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
+ 1:39:26 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
53
 
53
- 11:34:30 AM - 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
+ 1:39:26 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
55
 
55
- 11:34:30 AM - 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
+ 1:39:26 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
57
 
57
- 11:34:30 AM - 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'
58
+ 1:39:26 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'
58
59
 
59
- 11:34:30 AM - 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
+ 1:39:26 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
61
 
61
- 11:34:30 AM - Project '../keyring/tsconfig.json' is up to date because newest input '../keyring/src/pair/decode.ts' is older than output '../keyring/tsconfig.tsbuildinfo'
62
+ 1:39:26 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'
62
63
 
63
- 11:34:31 AM - Project '../types-env/tsconfig.json' is up to date because newest input '../types-env/src/tests/typesEnv.test-d.ts' is older than output '../types-env/tsconfig.tsbuildinfo'
64
+ 1:39:27 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
65
 
65
- 11:34:31 AM - Project '../env/tsconfig.json' is up to date because newest input '../env/src/env.ts' is older than output '../env/tsconfig.tsbuildinfo'
66
+ 1:39:27 PM - Project '../env/tsconfig.json' is up to date because newest input '../env/src/index.ts' is older than output '../env/tsconfig.tsbuildinfo'
66
67
 
67
- 11:34:31 AM - Project '../api-express-router/tsconfig.json' is up to date because newest input '../api-express-router/src/tests/unit/testDoubles.ts' is older than output '../api-express-router/tsconfig.tsbuildinfo'
68
+ 1:39:27 PM - Project '../api-express-router/tsconfig.json' is up to date because newest input '../api-express-router/src/tests/unit/apiExpressRouterFactory.unit.test.ts' is older than output '../api-express-router/tsconfig.tsbuildinfo'
68
69
 
69
- 11:34:31 AM - Project '../datasets/tsconfig.json' is up to date because newest input '../datasets/src/index.ts' is older than output '../datasets/tsconfig.tsbuildinfo'
70
+ 1:39:27 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
71
 
71
- 11:34:31 AM - 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
+ 1:39:27 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
73
 
73
- 11:34:31 AM - Project '../provider/tsconfig.json' is up to date because newest input '../provider/src/util.ts' is older than output '../provider/tsconfig.tsbuildinfo'
74
+ 1:39:27 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
75
 
75
- 11:34:31 AM - Project '../../dev/workspace/tsconfig.json' is up to date because newest input '../../dev/workspace/src/tests/projectInfo.unit.test.ts' is older than output '../../dev/workspace/tsconfig.tsbuildinfo'
76
+ 1:39:27 PM - Project '../provider/tsconfig.json' is up to date because newest input '../provider/src/util.ts' is older than output '../provider/tsconfig.tsbuildinfo'
76
77
 
77
- 11:34:31 AM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
78
+ 1:39:27 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
79
 
79
- 11:34:31 AM - Building project '/home/runner/work/captcha/captcha/packages/cli/tsconfig.json'...
80
+ 1:39:27 PM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
81
+
82
+ 1:39:27 PM - Building project '/home/runner/work/captcha/captcha/packages/cli/tsconfig.json'...
80
83
 
package/.turbo/turbo-build.log CHANGED
@@ -1,9 +1,9 @@
1
1
 
2
- > @prosopo/cli@3.7.12 build
2
+ > @prosopo/cli@3.7.14 build
3
3
  > npm run build:cross-env -- --mode ${NODE_ENV:-development}
4
4
 
5
5
 
6
- > @prosopo/cli@3.7.12 build:cross-env
6
+ > @prosopo/cli@3.7.14 build:cross-env
7
7
  > vite build --config vite.esm.config.ts --mode production
8
8
 
9
9
  ViteEsmConfig: .
@@ -29,7 +29,8 @@ ViteEsmConfig: .
29
29
  '/home/runner/work/captcha/captcha/packages/provider/tsconfig.json',
30
30
  '/home/runner/work/captcha/captcha/packages/api-express-router/tsconfig.json',
31
31
  '/home/runner/work/captcha/captcha/packages/datasets/tsconfig.json',
32
- '/home/runner/work/captcha/captcha/packages/load-balancer/tsconfig.json'
32
+ '/home/runner/work/captcha/captcha/packages/load-balancer/tsconfig.json',
33
+ '/home/runner/work/captcha/captcha/packages/puzzle-assets/tsconfig.json'
33
34
  ]
34
35
  }
35
36
  {
@@ -54,7 +55,8 @@ ViteEsmConfig: .
54
55
  '@prosopo/provider',
55
56
  '@prosopo/api-express-router',
56
57
  '@prosopo/datasets',
57
- '@prosopo/load-balancer'
58
+ '@prosopo/load-balancer',
59
+ '@prosopo/puzzle-assets'
58
60
  ]
59
61
  }
60
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.
@@ -86,4 +88,4 @@ dist/commands/siteKeyRegister.js 3.30 kB │ gzip: 1.14 kB
86
88
  dist/prosopo.config.js 4.43 kB │ gzip: 1.47 kB
87
89
  dist/RateLimiter.js 5.16 kB │ gzip: 0.89 kB
88
90
 
89
- ✓ built in 32ms
91
+ ✓ built in 70ms
package/CHANGELOG.md CHANGED
@@ -1,5 +1,22 @@
1
1
  # @prosopo/cli
2
2
 
3
+ ## 3.7.14
4
+ ### Patch Changes
5
+
6
+ - Updated dependencies [35f640f]
7
+ - Updated dependencies [9e53a48]
8
+ - @prosopo/provider@5.3.0
9
+ - @prosopo/types@5.2.1
10
+ - @prosopo/api@4.0.9
11
+ - @prosopo/env@3.6.33
12
+ - @prosopo/keyring@2.9.72
13
+
14
+ ## 3.7.13
15
+ ### Patch Changes
16
+
17
+ - Updated dependencies [c2bfcb8]
18
+ - @prosopo/provider@5.2.1
19
+
3
20
  ## 3.7.12
4
21
  ### Patch Changes
5
22
 
package/Dockerfile CHANGED
@@ -14,13 +14,16 @@ RUN curl -L -o GeoLite2-Country.mmdb https://git.io/GeoLite2-Country.mmdb
14
14
  RUN curl -L -o GeoLite2-City.mmdb https://git.io/GeoLite2-City.mmdb
15
15
  RUN curl -L -o GeoLite2-ASN.mmdb https://git.io/GeoLite2-ASN.mmdb
16
16
 
17
- # make the provider cli executable
18
- # create a package.json file for the provider cli to force it to run in module mode and set the binary for npx
17
+ # make the provider cli executable and set the binary for npx. The
18
+ # generated package.json declares `sharp` as a runtime dependency so
19
+ # `npm i` installs the linux-x64 native binary — vite bundles the JS
20
+ # shim but not the platform-specific .node addon, and the puzzle
21
+ # renderer imports sharp from @prosopo/puzzle-assets at runtime.
22
+ # --os=linux --cpu=x64 --include=optional forces npm to fetch the
23
+ # correct optional platform variant regardless of the build host.
19
24
  RUN echo '#!/usr/bin/env node' | cat - provider.cli.bundle.js > temp && mv temp provider.cli.bundle.js && \
20
- echo '{ "name": "prosopo-provider", "bin": { "provider": "./provider.cli.bundle.js" }, "type": "module" }' > /usr/src/app/package.json
21
-
22
- # install the provider cli binary
23
- RUN npm i
25
+ echo '{ "name": "prosopo-provider", "bin": { "provider": "./provider.cli.bundle.js" }, "type": "module", "dependencies": { "sharp": "0.35.3" } }' > /usr/src/app/package.json && \
26
+ npm i --include=optional --os=linux --cpu=x64
24
27
 
25
28
  EXPOSE 9229 9339 80 443
26
29