Auto refactor Blade/Livewire component namespaces

[N1ebieski]

This PR adds automatic refactoring of Blade/Livewire component namespaces in every view file when:

• a component file is renamed
• a component folder is added
• a component file is moved to another folder

from within the VS Code Explorer.

Nagrywanie.ekranu.2026-04-08.213713.mp4

Roadmap

General

• Create a new RenameFilesProvider

Respositories

• Support for Blade components
• Support for Blade class components
  • Changing a class namespace should update the component view file
  • Changing a class namespace should update the view path in the render method
• Support for Livewire SFC/MFC components
• Support for Livewire class components
  • Changing a class namespace should update the component view file
  • Changing a class namespace should update the view path in the render method

Other

• Support for multi-root workspaces if Support for multi-root workspaces #624 is accepted
• Optimization
• Add configuration options to enable or disable Blade/Livewire features

Testing

• Write some VSCode tests

Summary

Hey @TitasGailius, this PR is ready for review. Some details:

• Drag & drop for Blade/Livewire class components requires manually updating the class namespace after dropping. It might be a good idea in the future (maybe via a framework-agnostic provider) to automatically refactor PHP class namespaces/imports in other PHP files
• If you use Intelephense or another PHP intelligence plugin, the Blade/Livewire class component can also be refactored by pressing F2 on the classname
• I tested this feature manually on Windows and Linux. macOS testing is still needed
• The performance is satisfactory. I tested the feature in one of my projects with hundreds of Blade components, and it worked very well. However, I think it would be better to replace vscode.workspace.findFiles with grep or something similar, because the VS Code team has still not implemented findTextInFiles in the stable version
• I wrote VS Code tests for Blade components using your laravel-react fixture. To test Livewire components, I would need to install the livewire package. Let me know if you’d like me to do that
• Support for multi-root workspaces is still pending. I’ll prepare a separate PR for this if this PR is accepted.