docs/3.guide/1.concepts/8.typescript.md (1)

106-117: Minor doc improvement: link to both tsConfig and nodeTsConfig API sections (and keep punctuation consistent).

The new section explains both options, but the ::read-more currently points only to the typescript.tsConfig API docs. Consider adding a second read-more (or expanding the existing one) to also link to typescript.nodeTsConfig for completeness.

Also, the static-analysis hints flag “loose punctuation mark” around Line 114 and Line 116—worth double-checking that list-item terminal punctuation is consistent with surrounding docs styles.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/3.guide/1.concepts/8.typescript.md` around lines 106 - 117, The docs
section links only to typescript.tsConfig but should also reference
typescript.nodeTsConfig and ensure list-item punctuation matches project style;
update the read-more block (or add a second read-more) so it links to both the
tsConfig and nodeTsConfig API pages, and adjust the terminal punctuation of the
two list items that mention "Nuxt app context" and "Node context" (references to
tsConfig and nodeTsConfig) to match surrounding documentation punctuation style;
locate and change the `typescript.tsConfig` and `typescript.nodeTsConfig`
mentions in the text and the `::read-more` helper to add the second link and fix
punctuation consistency.

docs/4.api/6.nuxt-config.md (1)

1543-1558: Minor clarity: explicitly state paths/globs are resolved relative to the generated .nuxt/*.json tsconfig location.

The new tsConfig example (include: ['../tests/**/*.ts']) will likely work, but Nuxt’s generated tsconfig files live under .nuxt/ (or buildDir). If include patterns are interpreted relative to the generated tsconfig file (as TS typically does), it’s worth a 1-line note like “paths are relative to the generated tsconfig location” to prevent confusion when users change buildDir.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/4.api/6.nuxt-config.md` around lines 1543 - 1558, Add a one-line
clarification to the `tsConfig` section noting that include paths/globs (e.g.,
the example `include: ['../tests/**/*.ts']`) are resolved relative to the
generated Nuxt tsconfig files under `.nuxt/` (or the configured `buildDir`), so
users should craft patterns accordingly if they change `buildDir`.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

docs/3.guide/1.concepts/8.typescript.md (2)

106-117: ⚡ Quick win

Make the “how” explicit: mention include globs in tsConfig/nodeTsConfig.

Right now the section tells users what to extend, but not the mechanism (i.e. that these options are where you add include entries/globs for the custom files). Adding a short one-liner after the two bullets would reduce confusion and help readers apply the guidance without needing to immediately jump to the API docs.

Suggested patch

 - **Node context** — For files that only use plain TypeScript/Node.js APIs and do not depend on Nuxt-specific features (e.g., build scripts, configuration utilities). Extend [`typescript.nodeTsConfig`](/docs/4.x/api/nuxt-config#nodetsconfig).
 +
 + In both cases, use the option’s `include` globs (or equivalent) to pull in files outside Nuxt’s standard directories (for example, anything under `tests/`).
 
 ::read-more{to="/docs/4.x/getting-started/testing#typescript-support-in-tests"}
 For test-specific examples, see TypeScript Support in Tests.
 ::

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/3.guide/1.concepts/8.typescript.md` around lines 106 - 117, Add a
clarifying one-liner after the two bullets that explains how to include custom
files by adding include globs to the TypeScript settings (i.e., add an "include"
array/glob patterns to typescript.tsConfig for Nuxt app-context files and to
typescript.nodeTsConfig for Node-context files) so readers know these options
are where to add their custom file globs.

---

115-117: 💤 Low value

Minor wording/casing consistency in the read-more callout.

“TypeScript Support in Tests” is capitalised like a title. If that’s meant to be a literal doc-title match, it’s fine; otherwise consider using sentence case (“TypeScript support in tests”) to stay consistent with the surrounding text.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/3.guide/1.concepts/8.typescript.md` around lines 115 - 117, The
::read-more callout text "TypeScript Support in Tests" uses title case; update
the callout to use sentence case for consistency with surrounding text by
changing that string to "TypeScript support in tests" in the ::read-more
invocation so the display text matches the desired casing.

docs/3.guide/1.concepts/8.typescript.md (2)

115-117: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Tighten the ::read-more block wording/punctuation to avoid doc lint warnings.

LanguageTool hints show “Loose punctuation mark” around the ::read-more block (near Line [116]). The current line ends with a period (“Tests.”) immediately before the directive is closed, which can trigger formatting/lint noise.

🛠️ Proposed change

 ::read-more{to="/docs/4.x/getting-started/testing#typescript-support-in-tests"}
-For test-specific examples, see TypeScript Support in Tests.
+For TypeScript support specifically in test files, see TypeScript Support in Tests.
 ::

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/3.guide/1.concepts/8.typescript.md` around lines 115 - 117, Tighten the
::read-more block punctuation by removing the trailing period inside the
directive text so it reads
::read-more{to="/docs/4.x/getting-started/testing#typescript-support-in-tests"}For
test-specific examples, see TypeScript Support in Tests::, or alternatively
place the sentence-ending period after the closing directive; update the
::read-more block (the directive targeting
"/docs/4.x/getting-started/testing#typescript-support-in-tests") accordingly to
avoid the “Loose punctuation mark” lint warning.

---

106-113: ⚠️ Potential issue | 🟠 Major

Fix incorrect config property name: use typescript.tsConfig (not typescript.TSConfig).

Line 112 references typescript.TSConfig (capital "TS"), but the correct Nuxt property is typescript.tsConfig (lowercase "ts"). Users copying the wrong property name will not have their custom files included in type-checking.

Fix

-  - **Nuxt app context** — For files that import from Vue, Nuxt, or use auto-imported composables (e.g., test files using `mount()` or `useNuxtApp()`). Extend [`typescript.TSConfig`](/docs/4.x/api/nuxt-config#tsconfig).
+  - **Nuxt app context** — For files that import from Vue, Nuxt, or use auto-imported composables (e.g., test files using `mount()` or `useNuxtApp()`). Extend [`typescript.tsConfig`](/docs/4.x/api/nuxt-config#tsconfig).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/3.guide/1.concepts/8.typescript.md` around lines 106 - 113, The
documentation incorrectly references the Nuxt config property as
typescript.TSConfig (capital "TS"); update the text to use the correct property
name typescript.tsConfig (lowercase "ts") wherever mentioned and ensure the
distinction versus typescript.nodeTsConfig remains clear so readers use
typescript.tsConfig for Nuxt app-context type-checking and
typescript.nodeTsConfig for Node-context files.