@prosopo/keyring 2.9.74 → 2.9.75

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 (6) hide show
  1. package/.turbo/turbo-build$colon$cjs.log +3 -3
  2. package/.turbo/turbo-build$colon$tsc.log +11 -11
  3. package/.turbo/turbo-build.log +4 -4
  4. package/CHANGELOG.md +6 -0
  5. package/package.json +2 -2
  6. package/tsconfig.tsbuildinfo +1 -1
package/.turbo/turbo-build$colon$cjs.log CHANGED
@@ -1,5 +1,5 @@
1
1
 
2
- > @prosopo/keyring@2.9.74 build:cjs
2
+ > @prosopo/keyring@2.9.75 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
- 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.
19
18
  '@prosopo/common',
20
19
  '@prosopo/locale',
21
20
  '@prosopo/logger',
@@ -24,6 +23,7 @@ ViteCommonJSConfig: .
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
  
@@ -44,4 +44,4 @@ dist/cjs/pair/decode.cjs 1.77 kB │ gzip: 0.70 kB
44
44
  dist/cjs/pair/index.cjs 7.26 kB │ gzip: 2.12 kB
45
45
  dist/cjs/keyring/keyring.cjs 11.14 kB │ gzip: 3.05 kB
46
46
 
47
- ✓ built in 78ms
47
+ ✓ built in 61ms
package/.turbo/turbo-build$colon$tsc.log CHANGED
@@ -1,8 +1,8 @@
1
1
 
2
- > @prosopo/keyring@2.9.74 build:tsc
2
+ > @prosopo/keyring@2.9.75 build:tsc
3
3
  > tsc --build --verbose
4
4
 
5
- 7:17:13 PM - Projects in this build:
5
+ 11:17:33 AM - Projects in this build:
6
6
  * ../../dev/config/tsconfig.json
7
7
  * ../locale/tsconfig.json
8
8
  * ../util/tsconfig.json
@@ -12,21 +12,21 @@
12
12
  * ../common/tsconfig.json
13
13
  * tsconfig.json
14
14
 
15
- 7:17:13 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'
15
+ 11:17:34 AM - Project '../../dev/config/tsconfig.json' is up to date because newest input '../../dev/config/src/vite/vite.frontend.config.ts' is older than output '../../dev/config/tsconfig.tsbuildinfo'
16
16
 
17
- 7:17:13 PM - Project '../locale/tsconfig.json' is up to date because newest input '../locale/src/translationKey.ts' is older than output '../locale/tsconfig.tsbuildinfo'
17
+ 11:17:34 AM - Project '../locale/tsconfig.json' is up to date because newest input '../locale/src/translationKey.ts' is older than output '../locale/tsconfig.tsbuildinfo'
18
18
 
19
- 7:17:13 PM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/url.ts' is older than output '../util/tsconfig.tsbuildinfo'
19
+ 11:17:34 AM - 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
- 7:17:13 PM - Project '../logger/tsconfig.json' is up to date because newest input '../logger/src/index.ts' is older than output '../logger/tsconfig.tsbuildinfo'
21
+ 11:17:34 AM - Project '../logger/tsconfig.json' is up to date because newest input '../logger/src/index.ts' is older than output '../logger/tsconfig.tsbuildinfo'
22
22
 
23
- 7:17:13 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
+ 11:17:34 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'
24
24
 
25
- 7:17:14 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
+ 11:17:34 AM - Project '../types/tsconfig.json' is up to date because newest input '../types/src/index.ts' is older than output '../types/tsconfig.tsbuildinfo'
26
26
 
27
- 7:17:14 PM - Project '../common/tsconfig.json' is up to date because newest input '../common/src/utils/batches.ts' is older than output '../common/tsconfig.tsbuildinfo'
27
+ 11:17:34 AM - Project '../common/tsconfig.json' is up to date because newest input '../common/src/error.ts' is older than output '../common/tsconfig.tsbuildinfo'
28
28
 
29
- 7:17:14 PM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
29
+ 11:17:34 AM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
30
30
 
31
- 7:17:14 PM - Building project '/home/runner/work/captcha/captcha/packages/keyring/tsconfig.json'...
31
+ 11:17:34 AM - Building project '/home/runner/work/captcha/captcha/packages/keyring/tsconfig.json'...
32
32
 
package/.turbo/turbo-build.log CHANGED
@@ -1,9 +1,9 @@
1
1
 
2
- > @prosopo/keyring@2.9.74 build
2
+ > @prosopo/keyring@2.9.75 build
3
3
  > npm run build:cross-env -- --mode ${NODE_ENV:-development}
4
4
 
5
5
 
6
- > @prosopo/keyring@2.9.74 build:cross-env
6
+ > @prosopo/keyring@2.9.75 build:cross-env
7
7
  > vite build --config vite.esm.config.ts --mode production
8
8
 
9
9
  ViteEsmConfig: .
@@ -17,6 +17,7 @@ ViteEsmConfig: .
17
17
  '/home/runner/work/captcha/captcha/packages/util-crypto/tsconfig.json'
18
18
  ]
19
19
  }
20
+ 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
21
  {
21
22
  externals: [
22
23
  '@prosopo/common',
@@ -27,7 +28,6 @@ ViteEsmConfig: .
27
28
  '@prosopo/util-crypto'
28
29
  ]
29
30
  }
30
- 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.
31
31
  vite v8.1.5 building ssr environment for production...
32
32
  Bundle build started
33
33
  
@@ -49,4 +49,4 @@ dist/pair/decode.js 1.48 kB │ gzip: 0.66 kB
49
49
  dist/pair/index.js 6.96 kB │ gzip: 2.09 kB
50
50
  dist/keyring/keyring.js 10.74 kB │ gzip: 2.99 kB
51
51
 
52
- ✓ built in 86ms
52
+ ✓ built in 67ms
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # @prosopo/keyring
2
2
 
3
+ ## 2.9.75
4
+ ### Patch Changes
5
+
6
+ - Updated dependencies [c629c01]
7
+ - @prosopo/types@5.2.4
8
+
3
9
  ## 2.9.74
4
10
  ### Patch Changes
5
11
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@prosopo/keyring",
3
- "version": "2.9.74",
3
+ "version": "2.9.75",
4
4
  "description": "Keypair generator for Prosopo",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -40,7 +40,7 @@
40
40
  "@polkadot/util": "13.5.7",
41
41
  "@polkadot/util-crypto": "13.5.7",
42
42
  "@prosopo/common": "3.1.50",
43
- "@prosopo/types": "5.2.3",
43
+ "@prosopo/types": "5.2.4",
44
44
  "@prosopo/util": "3.3.6",
45
45
  "@prosopo/util-crypto": "13.5.30",
46
46
  "dotenv": "16.4.5"