Fixes a debug assertion failure that occurred when using "Move to File" or "Move to new File" refactor on React components and other symbols that don't have a parent but aren't module symbols.

Problem

The refactor would fail with:

Debug Failure. False expression: Expected symbol to be a moduleError: Debug Failure. False expression: Expected symbol to be a module    at Object.addImportForModuleSymbol

Root Cause

Insrc/services/refactors/helpers.ts, the logic assumed that iftargetSymbol.parent === undefined, then the symbol must be a module symbol. This assumption is incorrect for React components and other symbols that might not have a parent but are not modules.

Solution

Added a proper check forSymbolFlags.Module before callingaddImportForModuleSymbol:

// Beforeelseif(targetSymbol.parent===undefined){importAdder.addImportForModuleSymbol(symbol,isValidTypeOnlyUseSite,declaration);}// Afterelseif(targetSymbol.parent===undefined&&(targetSymbol.flags&SymbolFlags.Module)){importAdder.addImportForModuleSymbol(symbol,isValidTypeOnlyUseSite,declaration);}

This ensures that only actual module symbols are passed toaddImportForModuleSymbol, preventing the debug assertion failure.

Testing

• ✅ All 6300+ fourslash tests continue to pass
• ✅ Added test casemoveToNewFileSymbolWithoutParent.ts to validate the fix
• ✅ Linting and formatting checks pass

The fix is minimal and surgical, only adding the necessary validation without affecting existing functionality.

Fixes#62029.

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Clickhere to start the survey.