@prosopo/database 4.2.8 → 4.2.9

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.
@@ -51,4 +51,4 @@ dist/cjs/databases/captcha.cjs 8.23 kB │ gzip: 2.38 kB
51
51
  dist/cjs/redisCache.cjs 14.30 kB │ gzip: 4.45 kB
52
52
  dist/cjs/databases/provider.cjs 70.62 kB │ gzip: 13.47 kB
53
53
 
54
- ✓ built in 98ms
54
+ ✓ built in 65ms
@@ -1,5 +1,5 @@
1
1
  $ tsc --build --verbose
2
- 5:08:27 PM - Projects in this build:
2
+ 7:40:57 PM - Projects in this build:
3
3
  * ../../dev/config/tsconfig.json
4
4
  * ../util/tsconfig.json
5
5
  * ../locale/tsconfig.json
@@ -14,31 +14,31 @@ $ tsc --build --verbose
14
14
  * ../types-database/tsconfig.json
15
15
  * tsconfig.json
16
16
 
17
- 5:08:27 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
+ 7:40:57 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'
18
18
 
19
- 5:08:27 PM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/url.ts' is older than output '../util/tsconfig.tsbuildinfo'
19
+ 7:40:57 PM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/url.ts' is older than output '../util/tsconfig.tsbuildinfo'
20
20
 
21
- 5:08:27 PM - Project '../locale/tsconfig.json' is up to date because newest input '../locale/src/translationKey.ts' is older than output '../locale/tsconfig.tsbuildinfo'
21
+ 7:40:57 PM - Project '../locale/tsconfig.json' is up to date because newest input '../locale/src/process.ts' is older than output '../locale/tsconfig.tsbuildinfo'
22
22
 
23
- 5:08:27 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'
23
+ 7:40:57 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'
24
24
 
25
- 5:08:27 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'
25
+ 7:40:57 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'
26
26
 
27
- 5:08:27 PM - Project '../common/tsconfig.json' is up to date because newest input '../common/src/errorCodes.ts' is older than output '../common/tsconfig.tsbuildinfo'
27
+ 7:40:57 PM - Project '../common/tsconfig.json' is up to date because newest input '../common/src/tests/utils/objectUtils.unit.test.ts' is older than output '../common/tsconfig.tsbuildinfo'
28
28
 
29
- 5:08:27 PM - Project '../logger/tsconfig.json' is up to date because newest input '../logger/src/index.ts' is older than output '../logger/tsconfig.tsbuildinfo'
29
+ 7:40:57 PM - Project '../logger/tsconfig.json' is up to date because newest input '../logger/src/tests/loggerBrowser.unit.test.ts' is older than output '../logger/tsconfig.tsbuildinfo'
30
30
 
31
- 5:08:27 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'
31
+ 7:40:57 PM - Project '../api-route/tsconfig.json' is up to date because newest input '../api-route/src/tests/apiRoute.unit.test.ts' is older than output '../api-route/tsconfig.tsbuildinfo'
32
32
 
33
- 5:08:27 PM - Project '../redis-client/tsconfig.json' is up to date because newest input '../redis-client/src/tests/redisIndex.integration.test.ts' is older than output '../redis-client/tsconfig.tsbuildinfo'
33
+ 7:40:57 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'
34
34
 
35
- 5:08:27 PM - Project '../api/tsconfig.json' is up to date because newest input '../api/src/index.ts' is older than output '../api/tsconfig.tsbuildinfo'
35
+ 7:40:57 PM - Project '../api/tsconfig.json' is up to date because newest input '../api/src/index.ts' is older than output '../api/tsconfig.tsbuildinfo'
36
36
 
37
- 5:08:27 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'
37
+ 7:40:57 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'
38
38
 
39
- 5:08:27 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'
39
+ 7:40:57 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'
40
40
 
41
- 5:08:27 PM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
41
+ 7:40:57 PM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
42
42
 
43
- 5:08:27 PM - Building project '/home/runner/work/captcha/captcha/packages/database/tsconfig.json'...
43
+ 7:40:57 PM - Building project '/home/runner/work/captcha/captcha/packages/database/tsconfig.json'...
44
44
 
@@ -16,7 +16,6 @@ ViteEsmConfig: .
16
16
  '/home/runner/work/captcha/captcha/packages/api/tsconfig.json'
17
17
  ]
18
18
  }
19
- 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.
20
19
  {
21
20
  externals: [
22
21
  '@prosopo/common',
@@ -32,6 +31,7 @@ ViteEsmConfig: .
32
31
  '@prosopo/api'
33
32
  ]
34
33
  }
34
+ 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.
35
35
  vite v8.1.6 building ssr environment for production...
36
36
  Bundle build started
37
37
  
@@ -52,4 +52,4 @@ dist/databases/captcha.js 8.17 kB │ gzip: 2.38 kB
52
52
  dist/redisCache.js 14.25 kB │ gzip: 4.43 kB
53
53
  dist/databases/provider.js 68.90 kB │ gzip: 13.47 kB
54
54
 
55
- ✓ built in 117ms
55
+ ✓ built in 140ms
package/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # @prosopo/database
2
2
 
3
+ ## 4.2.9
4
+ ### Patch Changes
5
+
6
+ - @prosopo/types@5.17.1
7
+ - @prosopo/types-database@5.11.1
8
+ - @prosopo/common@3.3.0
9
+ - @prosopo/user-access-policy@3.15.6
10
+
3
11
  ## 4.2.8
4
12
  ### Patch Changes
5
13
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@prosopo/database",
3
- "version": "4.2.8",
3
+ "version": "4.2.9",
4
4
  "description": "Prosopo database plugins for provider",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -31,9 +31,9 @@
31
31
  "@prosopo/common": "3.3.0",
32
32
  "@prosopo/logger": "2.1.5",
33
33
  "@prosopo/redis-client": "1.0.42",
34
- "@prosopo/types": "5.17.0",
35
- "@prosopo/types-database": "5.11.0",
36
- "@prosopo/user-access-policy": "3.15.5",
34
+ "@prosopo/types": "5.17.1",
35
+ "@prosopo/types-database": "5.11.1",
36
+ "@prosopo/user-access-policy": "3.15.6",
37
37
  "@prosopo/util": "3.3.16",
38
38
  "bson": "7.3.3",
39
39
  "make-dir": "5.1.0",