@prosopo/api 4.1.2 → 4.1.3

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/api@4.1.2 build:cjs
2
+ > @prosopo/api@4.1.3 build:cjs
3
3
  > NODE_ENV=${NODE_ENV:-development}; vite build --config vite.cjs.config.ts --mode $NODE_ENV
4
4
 
5
5
  ViteCommonJSConfig: .
@@ -33,4 +33,4 @@ dist/cjs/index.cjs 0.61 kB │ gzip: 0.24 kB
33
33
  dist/cjs/api/HttpClientBase.cjs 2.29 kB │ gzip: 0.61 kB
34
34
  dist/cjs/api/ProviderApi.cjs 14.10 kB │ gzip: 2.38 kB
35
35
 
36
- ✓ built in 56ms
36
+ ✓ built in 80ms
@@ -1,8 +1,8 @@
1
1
 
2
- > @prosopo/api@4.1.2 build:tsc
2
+ > @prosopo/api@4.1.3 build:tsc
3
3
  > tsc --build --verbose
4
4
 
5
- 6:46:59 PM - Projects in this build:
5
+ 10:01:59 PM - 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
- 6:46: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'
13
+ 10:02:00 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'
14
14
 
15
- 6:46:59 PM - Project '../locale/tsconfig.json' is up to date because newest input '../locale/src/translationKey.ts' is older than output '../locale/tsconfig.tsbuildinfo'
15
+ 10:02:00 PM - 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
- 6:46:59 PM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/url.ts' is older than output '../util/tsconfig.tsbuildinfo'
17
+ 10:02:00 PM - 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
- 6:46: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'
19
+ 10:02:00 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'
20
20
 
21
- 6:46: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'
21
+ 10:02:00 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'
22
22
 
23
- 6:46:59 PM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
23
+ 10:02:00 PM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
24
24
 
25
- 6:46:59 PM - Building project '/home/runner/work/captcha/captcha/packages/api/tsconfig.json'...
25
+ 10:02:00 PM - Building project '/home/runner/work/captcha/captcha/packages/api/tsconfig.json'...
26
26
 
@@ -1,9 +1,9 @@
1
1
 
2
- > @prosopo/api@4.1.2 build
2
+ > @prosopo/api@4.1.3 build
3
3
  > npm run build:cross-env -- --mode ${NODE_ENV:-development}
4
4
 
5
5
 
6
- > @prosopo/api@4.1.2 build:cross-env
6
+ > @prosopo/api@4.1.3 build:cross-env
7
7
  > vite build --config vite.esm.config.ts --mode production
8
8
 
9
9
  ViteEsmConfig: .
@@ -16,7 +16,6 @@ ViteEsmConfig: .
16
16
  ]
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
  externals: [
21
20
  '@prosopo/types',
22
21
  '@prosopo/locale',
@@ -24,6 +23,7 @@ ViteEsmConfig: .
24
23
  '@prosopo/util-crypto'
25
24
  ]
26
25
  }
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
27
  vite v8.1.5 building ssr environment for production...
28
28
  Bundle build started
29
29
  
@@ -38,4 +38,4 @@ dist/index.js 0.36 kB │ gzip: 0.18 kB
38
38
  dist/api/HttpClientBase.js 2.19 kB │ gzip: 0.60 kB
39
39
  dist/api/ProviderApi.js 12.39 kB │ gzip: 2.38 kB
40
40
 
41
- ✓ built in 32ms
41
+ ✓ built in 69ms
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # @prosopo/api
2
2
 
3
+ ## 4.1.3
4
+ ### Patch Changes
5
+
6
+ - Updated dependencies [458cf17]
7
+ - @prosopo/types@5.5.2
8
+
3
9
  ## 4.1.2
4
10
  ### Patch Changes
5
11
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@prosopo/api",
3
- "version": "4.1.2",
3
+ "version": "4.1.3",
4
4
  "description": "Wrapper for the provider API",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -39,7 +39,7 @@
39
39
  },
40
40
  "homepage": "https://github.com/prosopo/captcha#readme",
41
41
  "dependencies": {
42
- "@prosopo/types": "5.5.1"
42
+ "@prosopo/types": "5.5.2"
43
43
  },
44
44
  "devDependencies": {
45
45
  "@prosopo/config": "3.3.12",