@prosopo/datasets-fs 3.0.138 → 3.0.139
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.
- package/.turbo/turbo-build$colon$cjs.log +3 -3
- package/.turbo/turbo-build$colon$tsc.log +12 -12
- package/.turbo/turbo-build.log +4 -4
- package/CHANGELOG.md +9 -0
- package/README.md +2 -2
- package/package.json +2 -2
- package/tsconfig.tsbuildinfo +1 -1
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
|
|
2
|
-
> @prosopo/datasets-fs@3.0.
|
|
2
|
+
> @prosopo/datasets-fs@3.0.139 build:cjs
|
|
3
3
|
> NODE_ENV=${NODE_ENV:-development}; vite build --config vite.cjs.config.ts --mode $NODE_ENV
|
|
4
4
|
|
|
5
5
|
ViteCommonJSConfig: .
|
|
@@ -15,7 +15,6 @@ ViteCommonJSConfig: .
|
|
|
15
15
|
}
|
|
16
16
|
{
|
|
17
17
|
externals: [
|
|
18
|
-
[33mThe plugin "vite-tsconfig-paths" is detected. Vite now supports tsconfig paths resolution natively via the [1mresolve.tsconfigPaths[22m option. You can remove the plugin and set [1mresolve.tsconfigPaths: true[22m in your Vite config instead.[39m
|
|
19
18
|
'@prosopo/common',
|
|
20
19
|
'@prosopo/locale',
|
|
21
20
|
'@prosopo/util',
|
|
@@ -24,6 +23,7 @@ ViteCommonJSConfig: .
|
|
|
24
23
|
'@prosopo/util-crypto'
|
|
25
24
|
]
|
|
26
25
|
}
|
|
26
|
+
[33mThe plugin "vite-tsconfig-paths" is detected. Vite now supports tsconfig paths resolution natively via the [1mresolve.tsconfigPaths[22m option. You can remove the plugin and set [1mresolve.tsconfigPaths: true[22m in your Vite config instead.[39m
|
|
27
27
|
[36mvite v8.1.5 [32mbuilding ssr environment for production...[36m[39m
|
|
28
28
|
Bundle build started
|
|
29
29
|
[2K
|
|
@@ -34,7 +34,7 @@ dist/cjs/index.cjs 0.15 kB │ gzip: 0.14 kB
|
|
|
34
34
|
dist/cjs/_virtual/_rolldown/runtime.cjs 1.00 kB │ gzip: 0.50 kB
|
|
35
35
|
dist/cjs/cli/cli.cjs 1.74 kB │ gzip: 0.81 kB
|
|
36
36
|
|
|
37
|
-
[32m✓ built in
|
|
37
|
+
[32m✓ built in 75ms[39m
|
|
38
38
|
[copy-plugin] copying /home/runner/work/captcha/captcha/packages/datasets-fs/src/tests/data/flat/data.json to /home/runner/work/captcha/captcha/packages/datasets-fs/dist/tests/data/flat/data.json
|
|
39
39
|
[copy-plugin] copying /home/runner/work/captcha/captcha/packages/datasets-fs/src/tests/data/flat_resized/captchas_v1.json to /home/runner/work/captcha/captcha/packages/datasets-fs/dist/tests/data/flat_resized/captchas_v1.json
|
|
40
40
|
[copy-plugin] copying /home/runner/work/captcha/captcha/packages/datasets-fs/src/tests/data/flat_resized/captchas_v2.json to /home/runner/work/captcha/captcha/packages/datasets-fs/dist/tests/data/flat_resized/captchas_v2.json
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
|
|
2
|
-
> @prosopo/datasets-fs@3.0.
|
|
2
|
+
> @prosopo/datasets-fs@3.0.139 build:tsc
|
|
3
3
|
> tsc --build --verbose
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
3:36:59 PM - Projects in this build:
|
|
6
6
|
* ../../dev/config/tsconfig.json
|
|
7
7
|
* ../util/tsconfig.json
|
|
8
8
|
* ../locale/tsconfig.json
|
|
@@ -13,23 +13,23 @@
|
|
|
13
13
|
* ../../dev/workspace/tsconfig.json
|
|
14
14
|
* tsconfig.json
|
|
15
15
|
|
|
16
|
-
|
|
16
|
+
3:36:59 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'
|
|
17
17
|
|
|
18
|
-
|
|
18
|
+
3:36:59 PM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/url.ts' is older than output '../util/tsconfig.tsbuildinfo'
|
|
19
19
|
|
|
20
|
-
|
|
20
|
+
3:36:59 PM - Project '../locale/tsconfig.json' is up to date because newest input '../locale/src/translationKey.ts' is older than output '../locale/tsconfig.tsbuildinfo'
|
|
21
21
|
|
|
22
|
-
|
|
22
|
+
3:36:59 PM - Project '../logger/tsconfig.json' is up to date because newest input '../logger/src/index.ts' is older than output '../logger/tsconfig.tsbuildinfo'
|
|
23
23
|
|
|
24
|
-
|
|
24
|
+
3:36:59 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'
|
|
25
25
|
|
|
26
|
-
|
|
26
|
+
3:36:59 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'
|
|
27
27
|
|
|
28
|
-
|
|
28
|
+
3:36:59 PM - Project '../common/tsconfig.json' is up to date because newest input '../common/src/index.ts' is older than output '../common/tsconfig.tsbuildinfo'
|
|
29
29
|
|
|
30
|
-
|
|
30
|
+
3:36:59 PM - Project '../../dev/workspace/tsconfig.json' is up to date because newest input '../../dev/workspace/src/projectInfo.ts' is older than output '../../dev/workspace/tsconfig.tsbuildinfo'
|
|
31
31
|
|
|
32
|
-
|
|
32
|
+
3:36:59 PM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
|
|
33
33
|
|
|
34
|
-
|
|
34
|
+
3:36:59 PM - Building project '/home/runner/work/captcha/captcha/packages/datasets-fs/tsconfig.json'...
|
|
35
35
|
|
package/.turbo/turbo-build.log
CHANGED
|
@@ -1,9 +1,9 @@
|
|
|
1
1
|
|
|
2
|
-
> @prosopo/datasets-fs@3.0.
|
|
2
|
+
> @prosopo/datasets-fs@3.0.139 build
|
|
3
3
|
> npm run build:cross-env -- --mode ${NODE_ENV:-development}
|
|
4
4
|
|
|
5
5
|
|
|
6
|
-
> @prosopo/datasets-fs@3.0.
|
|
6
|
+
> @prosopo/datasets-fs@3.0.139 build:cross-env
|
|
7
7
|
> vite build --config vite.esm.config.ts --mode production
|
|
8
8
|
|
|
9
9
|
ViteEsmConfig: .
|
|
@@ -19,7 +19,6 @@ ViteEsmConfig: .
|
|
|
19
19
|
}
|
|
20
20
|
{
|
|
21
21
|
externals: [
|
|
22
|
-
[33mThe plugin "vite-tsconfig-paths" is detected. Vite now supports tsconfig paths resolution natively via the [1mresolve.tsconfigPaths[22m option. You can remove the plugin and set [1mresolve.tsconfigPaths: true[22m in your Vite config instead.[39m
|
|
23
22
|
'@prosopo/common',
|
|
24
23
|
'@prosopo/locale',
|
|
25
24
|
'@prosopo/util',
|
|
@@ -28,6 +27,7 @@ ViteEsmConfig: .
|
|
|
28
27
|
'@prosopo/util-crypto'
|
|
29
28
|
]
|
|
30
29
|
}
|
|
30
|
+
[33mThe plugin "vite-tsconfig-paths" is detected. Vite now supports tsconfig paths resolution natively via the [1mresolve.tsconfigPaths[22m option. You can remove the plugin and set [1mresolve.tsconfigPaths: true[22m in your Vite config instead.[39m
|
|
31
31
|
[36mvite v8.1.5 [32mbuilding ssr environment for production...[36m[39m
|
|
32
32
|
Bundle build started
|
|
33
33
|
[2K
|
|
@@ -38,7 +38,7 @@ dist/_virtual/_rolldown/runtime.js 0.04 kB │ gzip: 0.06 kB
|
|
|
38
38
|
dist/index.js 0.09 kB │ gzip: 0.09 kB
|
|
39
39
|
dist/cli/cli.js 1.52 kB │ gzip: 0.73 kB
|
|
40
40
|
|
|
41
|
-
[32m✓ built in
|
|
41
|
+
[32m✓ built in 72ms[39m
|
|
42
42
|
[copy-plugin] copying /home/runner/work/captcha/captcha/packages/datasets-fs/src/tests/data/flat/data.json to /home/runner/work/captcha/captcha/packages/datasets-fs/dist/tests/data/flat/data.json
|
|
43
43
|
[copy-plugin] copying /home/runner/work/captcha/captcha/packages/datasets-fs/src/tests/data/flat_resized/captchas_v1.json to /home/runner/work/captcha/captcha/packages/datasets-fs/dist/tests/data/flat_resized/captchas_v1.json
|
|
44
44
|
[copy-plugin] copying /home/runner/work/captcha/captcha/packages/datasets-fs/src/tests/data/flat_resized/captchas_v2.json to /home/runner/work/captcha/captcha/packages/datasets-fs/dist/tests/data/flat_resized/captchas_v2.json
|
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,14 @@
|
|
|
1
1
|
# @prosopo/datasets-fs
|
|
2
2
|
|
|
3
|
+
## 3.0.139
|
|
4
|
+
### Patch Changes
|
|
5
|
+
|
|
6
|
+
- Updated dependencies [fda0eba]
|
|
7
|
+
- Updated dependencies [1728cd0]
|
|
8
|
+
- Updated dependencies [20542d8]
|
|
9
|
+
- Updated dependencies [eebe6ee]
|
|
10
|
+
- @prosopo/types@5.10.2
|
|
11
|
+
|
|
3
12
|
## 3.0.138
|
|
4
13
|
### Patch Changes
|
|
5
14
|
|
package/README.md
CHANGED
|
@@ -126,7 +126,7 @@ counts instead of `--count`.
|
|
|
126
126
|
|
|
127
127
|
```bash
|
|
128
128
|
docker compose cp ./captchas.json provider:/usr/src/app/captchas.json
|
|
129
|
-
docker compose exec provider
|
|
129
|
+
docker compose exec provider /nodejs/bin/node /usr/src/app/provider.cli.bundle.js provider_set_data_set --file /usr/src/app/captchas.json
|
|
130
130
|
docker compose restart provider
|
|
131
131
|
```
|
|
132
132
|
|
|
@@ -137,7 +137,7 @@ dataset uploaded into a running provider is stored but not served — image chal
|
|
|
137
137
|
Then register your site key for image captchas:
|
|
138
138
|
|
|
139
139
|
```bash
|
|
140
|
-
docker compose exec provider
|
|
140
|
+
docker compose exec provider /nodejs/bin/node /usr/src/app/provider.cli.bundle.js site_key_register <sitekey> enterprise \
|
|
141
141
|
--captcha_type image --domains example.com \
|
|
142
142
|
--pow_difficulty 4 --frictionless_threshold 0.5 --image_threshold 0.8
|
|
143
143
|
```
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@prosopo/datasets-fs",
|
|
3
|
-
"version": "3.0.
|
|
3
|
+
"version": "3.0.139",
|
|
4
4
|
"author": "PROSOPO LIMITED <info@prosopo.io>",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"private": false,
|
|
@@ -32,7 +32,7 @@
|
|
|
32
32
|
"@noble/hashes": "2.4.0",
|
|
33
33
|
"@prosopo/common": "3.1.59",
|
|
34
34
|
"@prosopo/logger": "2.1.0",
|
|
35
|
-
"@prosopo/types": "5.10.
|
|
35
|
+
"@prosopo/types": "5.10.2",
|
|
36
36
|
"@prosopo/util": "3.3.11",
|
|
37
37
|
"@prosopo/util-crypto": "13.5.33",
|
|
38
38
|
"@prosopo/workspace": "3.2.1",
|