@prosopo/api-route 2.6.63 → 2.6.65

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 (5) hide show
  1. package/.turbo/turbo-build$colon$cjs.log +2 -2
  2. package/.turbo/turbo-build$colon$tsc.log +6 -6
  3. package/.turbo/turbo-build.log +2 -2
  4. package/CHANGELOG.md +17 -0
  5. package/package.json +6 -6
package/.turbo/turbo-build$colon$cjs.log CHANGED
@@ -8,7 +8,7 @@ ViteCommonJSConfig: .
8
8
  }
9
9
  { externals: [ '@prosopo/logger', '@prosopo/util' ] }
10
10
  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.
11
- vite v8.1.5 building ssr environment for production...
11
+ vite v8.1.6 building ssr environment for production...
12
12
  Bundle build started
13
13
  
14
14
  ✓ 5 modules transformed.
@@ -19,4 +19,4 @@ dist/cjs/endpoint/.export.cjs 0.18 kB │ gzip: 0.09 kB
19
19
  dist/cjs/index.cjs 0.26 kB │ gzip: 0.15 kB
20
20
  dist/cjs/endpoint/apiEndpointResponseStatus.cjs 0.43 kB │ gzip: 0.19 kB
21
21
 
22
- ✓ built in 33ms
22
+ ✓ built in 55ms
package/.turbo/turbo-build$colon$tsc.log CHANGED
@@ -1,17 +1,17 @@
1
1
  $ tsc --build --verbose
2
- 1:37:24 PM - Projects in this build:
2
+ 5:07:37 PM - Projects in this build:
3
3
  * ../../dev/config/tsconfig.json
4
4
  * ../util/tsconfig.json
5
5
  * ../logger/tsconfig.json
6
6
  * tsconfig.json
7
7
 
8
- 1:37:24 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'
8
+ 5:07:37 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'
9
9
 
10
- 1:37:24 PM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/url.ts' is older than output '../util/tsconfig.tsbuildinfo'
10
+ 5:07:37 PM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/url.ts' is older than output '../util/tsconfig.tsbuildinfo'
11
11
 
12
- 1:37:24 PM - Project '../logger/tsconfig.json' is up to date because newest input '../logger/src/index.ts' is older than output '../logger/tsconfig.tsbuildinfo'
12
+ 5:07:37 PM - Project '../logger/tsconfig.json' is up to date because newest input '../logger/src/index.ts' is older than output '../logger/tsconfig.tsbuildinfo'
13
13
 
14
- 1:37:24 PM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
14
+ 5:07:37 PM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
15
15
 
16
- 1:37:24 PM - Building project '/home/runner/work/captcha/captcha/packages/api-route/tsconfig.json'...
16
+ 5:07:37 PM - Building project '/home/runner/work/captcha/captcha/packages/api-route/tsconfig.json'...
17
17
 
package/.turbo/turbo-build.log CHANGED
@@ -9,7 +9,7 @@ ViteEsmConfig: .
9
9
  }
10
10
  { externals: [ '@prosopo/logger', '@prosopo/util' ] }
11
11
  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.
12
- vite v8.1.5 building ssr environment for production...
12
+ vite v8.1.6 building ssr environment for production...
13
13
  Bundle build started
14
14
  
15
15
  ✓ 5 modules transformed.
@@ -21,4 +21,4 @@ dist/endpoint/.export.js 0.11 kB │ gzip: 0.08 kB
21
21
  dist/index.js 0.16 kB │ gzip: 0.11 kB
22
22
  dist/endpoint/apiEndpointResponseStatus.js 0.41 kB │ gzip: 0.19 kB
23
23
 
24
- ✓ built in 69ms
24
+ ✓ built in 63ms
package/CHANGELOG.md CHANGED
@@ -1,5 +1,22 @@
1
1
  # @prosopo/api-route
2
2
 
3
+ ## 2.6.65
4
+ ### Patch Changes
5
+
6
+ - 46b97b7: Roll up the open Dependabot updates: express 5 (with `@types/express` 5), dotenv 18, undici 8, geolib 4, vitest 5, vite 8.1.6 everywhere, 17 minor and patch bumps (Babel, mongoose, i18next, ip-address, turbo and others), `@angular/router` in the Angular demo, and a GitHub Actions bump.
7
+
8
+ The whole vitest family moves to 5.0.4, including `@vitest/coverage-v8`, because `@vitest/browser-playwright` 5 only works with vitest 5. The `@types/express-serve-static-core` override moves to 5.1.3 to match `@types/express` 5.
9
+
10
+ `@prosopo/dotenv` now loads env files with `quiet: true`. Since dotenv 17, every load prints an "injected env" line to stderr unless told not to.
11
+ - Updated dependencies [46b97b7]
12
+ - Updated dependencies [d2148c8]
13
+ - @prosopo/logger@2.1.5
14
+
15
+ ## 2.6.64
16
+ ### Patch Changes
17
+
18
+ - @prosopo/logger@2.1.4
19
+
3
20
  ## 2.6.63
4
21
  ### Patch Changes
5
22
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@prosopo/api-route",
3
- "version": "2.6.63",
3
+ "version": "2.6.65",
4
4
  "main": "dist/index.js",
5
5
  "types": "dist/index.d.ts",
6
6
  "type": "module",
@@ -15,17 +15,17 @@
15
15
  }
16
16
  },
17
17
  "dependencies": {
18
- "@prosopo/logger": "2.1.3",
18
+ "@prosopo/logger": "2.1.5",
19
19
  "zod": "3.23.8"
20
20
  },
21
21
  "devDependencies": {
22
- "@prosopo/config": "3.4.3",
22
+ "@prosopo/config": "3.5.0",
23
23
  "@types/node": "22.10.2",
24
- "@vitest/coverage-v8": "4.1.11",
24
+ "@vitest/coverage-v8": "5.0.4",
25
25
  "del-cli": "6.0.0",
26
26
  "typescript": "5.6.2",
27
- "vite": "8.1.5",
28
- "vitest": "4.1.11"
27
+ "vite": "8.1.6",
28
+ "vitest": "5.0.4"
29
29
  },
30
30
  "author": "PROSOPO LIMITED <info@prosopo.io>",
31
31
  "license": "Apache-2.0",