Did you create your component via the right click context menu in VS Code? It's possible that there's a missing configuration file either among the component files or in your local project. Try recreating the component through that method and make sure the files are saved locally.
In sandbox, replace code in class that has no code coverage with few lines of dummy code
In sandbox, create test class to cover few lines of dummy code
Deploy class and test class ...
The easiest solution is to create a new Apex Class via VS Code as per sfdcdox's answer above, then copy the contents of your file 'LightningComponentBundle' into it. Delete the original from Project and Org and then rename your new class as needed.
Alternatively you can create the class via the developer console in your org and then retrieve the metadata as ...
The error means you're missing a metadata file. On the file explorer, click on the New File button, and name it:
And give it the following contents:
<?xml version="1.0" encoding="UTF-8'?>
Technically, there is a way but it is weird and based on the aforementioned background processes:
This is obviously not ...
There's a different login flow that's intended for other devices where this local webserver setup isn't feasible, but it's actually a great way of dealing with this exact issue on desktops too!
You may need to use the command line directly instead of invoking via the command palette, but it's a simple command:
It gives you a code ...
I built my own VSCode Extension that I use for the requirements until the Salesforce official extension pack supports this as Generally Available.
Allow quicksaving to org upon saving
If the code in the server is different than local copy the save is stopped and a compare view is given that shows the difference between local copy and server copy.
Automatic conflict detection is available in beta for some commands only:
Select File > Preferences > Settings (Windows or Linux) or Code > Preferences > Settings (macOS).
Under Salesforce Feature Previews, select Detect Conflicts At Sync.
You can also enter conflict ...
Usually this kind of issues are due to sfdx updates by salesforce, first step would be to updating SFDX with sfdx update command.
If that doesn't work, try to uninstall the salesforcedx Plug-In with below command and install it again.
sfdx plugins:uninstall salesforcedx
Edit: There is an issue on Salesforce CLI github project which mentions this.