Console Warning: `Vue received a Component that was made a reactive object. This can lead to unnecessary performance overhead and should be avoided by marking the component with `markRaw` or using `shallowRef` instead of `ref`. `

[richard-cox]

Setup

• Rancher version: v2.15 dev of

Describe the bug

• home page console warning, appears at least twice per visit

my-logger.ts:26 [Vue warn]: Vue received a Component that was made a reactive object. This can lead to unnecessary performance overhead and should be avoided by marking the component with `markRaw` or using `shallowRef` instead of `ref`. 
Component that was made reactive:  {name: 'AsyncComponentWrapper', __asyncLoader: ƒ, __asyncHydrate: ƒ, setup: ƒ} 
  at <Header key=0 simple=true > 
  at <Home onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< undefined > > 
  at <RouterView> 
  at <App>

To Reproduce

• open dev tools
• nav to home page

Expected Result

• no console warning

[github-actions]

🤖 Issue grooming analysis

This bug report is well-groomed and ready for triage. Here's the analysis against the checklist:

✅ Clear Problem Statement
The title and description clearly explain the bug: a Vue warning about reactive component objects appears at least twice per home page visit in Rancher v2.15 dev, indicating a performance-overhead anti-pattern.

✅ Acceptance Criteria
Clearly defined: no Vue reactive-component console warning should appear on the home page.

✅ Technical Details
The full warning text and stack trace are provided, including the component details (AsyncComponentWrapper with __asyncLoader, __asyncHydrate, setup properties). The Rancher version (v2.15 dev) is specified, and the warning references the file my-logger.ts:26.

✅ Reproducibility
Simple steps: open dev tools, navigate to home page. Expected vs. actual behavior is clearly stated.

This analysis was generated automatically based on the repository's grooming checklist.

Generated by Daily Issue Grooming · ◷