@prosopo/detector 3.5.13 → 3.5.15

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 (8) hide show
  1. package/.turbo/turbo-build$colon$cjs.log +15 -8
  2. package/.turbo/turbo-build$colon$tsc.log +9 -9
  3. package/.turbo/turbo-build.log +15 -8
  4. package/CHANGELOG.md +18 -0
  5. package/dist/_virtual/_rolldown/runtime.js +3 -0
  6. package/dist/cjs/index.cjs +8855 -3801
  7. package/dist/index.js +8853 -3803
  8. package/package.json +6 -6
package/.turbo/turbo-build$colon$cjs.log CHANGED
@@ -1,5 +1,5 @@
1
1
 
2
- > @prosopo/detector@3.5.13 build:cjs
2
+ > @prosopo/detector@3.5.15 build:cjs
3
3
  > NODE_ENV=${NODE_ENV:-development}; vite build --config vite.cjs.config.ts --mode $NODE_ENV
4
4
 
5
5
  ViteCommonJSConfig: .
@@ -19,12 +19,19 @@ ViteCommonJSConfig: .
19
19
  '@prosopo/util-crypto'
20
20
  ]
21
21
  }
22
- vite v6.4.1 building SSR bundle for production...
22
+ 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.
23
+ vite v8.1.5 building ssr environment for production...
23
24
  Bundle build started
24
- transforming...
25
- Build end
26
- ✓ 1 modules transformed.
27
- Entry module "src/index.js" is using named and default exports together. Consumers of your bundle will have to use `..default` to access the default export, which may not be what you want. Use `output.exports: "named"` to disable this warning.
25
+ 
26
+ ✓ 2 modules transformed.
28
27
  rendering chunks...
29
- dist/cjs/index.cjs 935.80 kB
30
- ✓ built in 1.10s
28
+ computing gzip size...
29
+ dist/cjs/index.cjs 940.30 kB │ gzip: 353.37 kB
30
+
31
+ [COMMONJS_VARIABLE_IN_ESM] The CommonJS `module` variable is treated as a global variable in an ECMAScript module and may not work as expected
32
+ - in src/index.js at 846915..846921
33
+ - This file is considered to be an ECMAScript module because of the `export` keyword here: in src/index.js at 880799..880805
34
+ 
35
+ [MIXED_EXPORTS] Entry module "src/index.js" is using named (including "default", "encryptData") and default exports together. Consumers of your bundle will have to use `..default` to access the default export, which may not be what you want. Use `output.exports: "named"` to disable this warning.
36
+ 
37
+ ✓ built in 207ms
package/.turbo/turbo-build$colon$tsc.log CHANGED
@@ -1,8 +1,8 @@
1
1
 
2
- > @prosopo/detector@3.5.13 build:tsc
2
+ > @prosopo/detector@3.5.15 build:tsc
3
3
  > tsc --build --verbose
4
4
 
5
- 10:22:18 PM - Projects in this build:
5
+ 11:09:53 AM - Projects in this build:
6
6
  * ../../dev/config/tsconfig.json
7
7
  * ../locale/tsconfig.json
8
8
  * ../util/tsconfig.json
@@ -10,17 +10,17 @@
10
10
  * ../types/tsconfig.json
11
11
  * tsconfig.json
12
12
 
13
- 10:22:18 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'
13
+ 11:09:53 AM - 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'
14
14
 
15
- 10:22:18 PM - Project '../locale/tsconfig.json' is up to date because newest input '../locale/src/translationKey.ts' is older than output '../locale/tsconfig.tsbuildinfo'
15
+ 11:09:54 AM - Project '../locale/tsconfig.json' is up to date because newest input '../locale/src/translationKey.ts' is older than output '../locale/tsconfig.tsbuildinfo'
16
16
 
17
- 10:22:18 PM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/url.ts' is older than output '../util/tsconfig.tsbuildinfo'
17
+ 11:09:54 AM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/url.ts' is older than output '../util/tsconfig.tsbuildinfo'
18
18
 
19
- 10:22:18 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'
19
+ 11:09:54 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'
20
20
 
21
- 10:22:18 PM - Project '../types/tsconfig.json' is up to date because newest input '../types/src/procaptcha/api.ts' is older than output '../types/tsconfig.tsbuildinfo'
21
+ 11:09:54 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'
22
22
 
23
- 10:22:18 PM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
23
+ 11:09:54 AM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
24
24
 
25
- 10:22:18 PM - Building project '/home/runner/work/captcha/captcha/packages/detector/tsconfig.json'...
25
+ 11:09:54 AM - Building project '/home/runner/work/captcha/captcha/packages/detector/tsconfig.json'...
26
26
 
package/.turbo/turbo-build.log CHANGED
@@ -1,9 +1,9 @@
1
1
 
2
- > @prosopo/detector@3.5.13 build
2
+ > @prosopo/detector@3.5.15 build
3
3
  > npm run build:cross-env -- --mode ${NODE_ENV:-development}
4
4
 
5
5
 
6
- > @prosopo/detector@3.5.13 build:cross-env
6
+ > @prosopo/detector@3.5.15 build:cross-env
7
7
  > vite build --config vite.esm.config.ts --mode production
8
8
 
9
9
  ViteEsmConfig: .
@@ -23,11 +23,18 @@ ViteEsmConfig: .
23
23
  '@prosopo/util-crypto'
24
24
  ]
25
25
  }
26
- vite v6.4.1 building SSR bundle for production...
26
+ 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.
27
+ vite v8.1.5 building ssr environment for production...
27
28
  Bundle build started
28
- transforming...
29
- Build end
30
- ✓ 1 modules transformed.
29
+ 
30
+ ✓ 2 modules transformed.
31
31
  rendering chunks...
32
- dist/index.js 935.67 kB
33
- ✓ built in 1.31s
32
+ computing gzip size...
33
+ dist/_virtual/_rolldown/runtime.js 0.04 kB │ gzip: 0.06 kB
34
+ dist/index.js 940.23 kB │ gzip: 353.35 kB
35
+
36
+ [COMMONJS_VARIABLE_IN_ESM] The CommonJS `module` variable is treated as a global variable in an ECMAScript module and may not work as expected
37
+ - in src/index.js at 846915..846921
38
+ - This file is considered to be an ECMAScript module because of the `export` keyword here: in src/index.js at 880799..880805
39
+ 
40
+ ✓ built in 169ms
package/CHANGELOG.md CHANGED
@@ -1,5 +1,23 @@
1
1
  # @prosopo/detector
2
2
 
3
+ ## 3.5.15
4
+ ### Patch Changes
5
+
6
+ - Updated dependencies [787017b]
7
+ - Updated dependencies [787017b]
8
+ - Updated dependencies [787017b]
9
+ - Updated dependencies [6f19cde]
10
+ - @prosopo/types@5.0.0
11
+
12
+ ## 3.5.14
13
+ ### Patch Changes
14
+
15
+ - e14fce6: chore(deps): bump vite to 6.4.3 and mongoose to 8.24.1, and adjust types for the mongoose 8.24 Document/ObjectId changes
16
+ - Updated dependencies [103318c]
17
+ - Updated dependencies [270a8d8]
18
+ - Updated dependencies [e14fce6]
19
+ - @prosopo/types@4.10.0
20
+
3
21
  ## 3.5.13
4
22
  ### Patch Changes
5
23
 
package/dist/_virtual/_rolldown/runtime.js ADDED
@@ -0,0 +1,3 @@
1
+ import "node:module";
2
+ //#endregion
3
+ export {};