src/runtime-utils/utils/suspended.ts (1)

231-238: Potential loss of nested config properties other than globalProperties.

The current merge only explicitly handles globalProperties within config. If options.config contains additional nested objects like compilerOptions, the spread ...options.config will overwrite ...defaults.config entirely for those keys rather than deep-merging them.

Given the test at line 578-599 uses config.compilerOptions and the defaults don't set compilerOptions, this works now. However, if future defaults include compilerOptions, the user-provided values would fully replace defaults instead of merging.

If deep-merging other config sub-properties is intended, consider extending the pattern used for globalProperties.

♻️ Optional: extend deep merge for compilerOptions if needed

     config: {
       ...defaults.config,
       ...options.config,
       globalProperties: {
         ...defaults.config?.globalProperties,
         ...options.config?.globalProperties,
       } as NonNullable<typeof options['config']>['globalProperties'],
+      compilerOptions: {
+        ...defaults.config?.compilerOptions,
+        ...options.config?.compilerOptions,
+      },
     },

🤖 Prompt for AI Agents

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

In `@src/runtime-utils/utils/suspended.ts` around lines 231 - 238, The config
merge currently only deep-merges globalProperties and shallowly spreads
options.config over defaults.config, which will cause nested config objects
(e.g., compilerOptions) to be overwritten rather than merged; update the merge
logic around config to deep-merge any nested sub-objects you want preserved (at
least include compilerOptions like globalProperties) by merging defaults.config,
options.config, and then individually deep-merging nested keys such as
globalProperties and compilerOptions (referencing the existing defaults.config,
options.config, globalProperties, and compilerOptions symbols) so user-provided
nested settings are merged with defaults rather than replaced.

examples/app-vitest-full/tests/nuxt/compatibility-mount.spec.ts (1)

601-622: Consider adding tests for mocks and directives global options.

The new mergeComponentMountingGlobalOptions function also handles mocks and directives, but there are no dedicated tests in this suite for those options. While mocks is tested in the existing global.mocks test (line 48-57), adding explicit tests here would ensure comprehensive coverage of the merge behavior.

This is optional since the existing test at line 48 does cover mocks behavior.

🤖 Prompt for AI Agents

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

In `@examples/app-vitest-full/tests/nuxt/compatibility-mount.spec.ts` around lines
601 - 622, Add explicit tests for global.mocks and global.directives in this
compatibility-mount.spec.ts suite similar to the existing
config.globalProperties test: create a small Component via defineComponent that
uses a mocked property (e.g., this.$mocked or a template reference) and a custom
directive (e.g., v-test that mutates DOM/text), then mount it with options typed
as Options<typeof Component> and compare outputs from mount(...) and await
mountSuspended(...). Ensure the tests exercise the
mergeComponentMountingGlobalOptions behavior by passing mocks and directives
under the global option and asserting vWrapper.html() === nWrapper.html();
reference mount, mountSuspended, defineComponent, Options and
mergeComponentMountingGlobalOptions to locate where to add them.

examples/app-vitest-full/tests/nuxt/compatibility-mount.spec.ts (1)

586-590: Minor: el.textContent can be null in TypeScript.

Element.textContent has type string | null. While the test template guarantees content exists, adding a non-null assertion or fallback would be more defensive.

♻️ Proposed fix

           directives: {
             repeatText: {
               beforeMount(el: Element, { value }: { value: number }) {
-                el.textContent = el.textContent.repeat(value)
+                el.textContent = (el.textContent ?? '').repeat(value)
               },
             },
           },

🤖 Prompt for AI Agents

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

In `@examples/app-vitest-full/tests/nuxt/compatibility-mount.spec.ts` around lines
586 - 590, The custom directive repeatText's beforeMount handler uses
el.textContent which is typed as string | null; update the handler
(repeatText.beforeMount) to guard against null by either using a non-null
assertion (el.textContent!) or providing a fallback (e.g., (el.textContent ??
'') ) before calling .repeat(value) so TypeScript no longer reports a possible
null access.