Skip to content

fix: use generated tsconfig and virtual file augmentations #6708

fix: use generated tsconfig and virtual file augmentations

fix: use generated tsconfig and virtual file augmentations #6708

Triggered via pull request September 19, 2024 10:31
Status Failure
Total duration 1m 44s
Artifacts

ci.yml

on: pull_request
Matrix: build
Matrix: lint
Matrix: test
Matrix: edge-release
Fit to window
Zoom out
Zoom in

Annotations

7 errors
Test on Node.js 18: src/utils.ts#L562
Argument of type '"i18n:registerModule"' is not assignable to parameter of type 'HookKeys<NuxtHooks>'.
Test on Node.js 18: src/utils.ts#L607
Property 'i18n' does not exist on type 'NuxtConfig & { srcDir: string; rootDir: string; }'.
Test on Node.js 18: src/utils.ts#L608
Property 'i18n' does not exist on type 'NuxtConfig & { srcDir: string; rootDir: string; }'.
Test on Node.js 18: src/utils.ts#L620
Property 'i18n' does not exist on type 'NuxtConfig & { srcDir: string; rootDir: string; }'.
Test on Node.js 18: src/utils.ts#L620
Property 'i18n' does not exist on type 'NuxtConfig & { srcDir: string; rootDir: string; }'.
Test on Node.js 18: test/gen.test.ts#L52
Conversion of type '{ options: { _layers: { config: { i18n: { locales: LocaleInfo[]; }; }; }[]; }; }' to type 'Nuxt' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
Test on Node.js 18
Process completed with exit code 1.