sfdx force:source:deploy --manifest ERROR: Cannot read property 'getMetadataName' of undefined. about cli HOT 5 CLOSED

I'll just add that perhaps the easiest and best solution is to just add to that Warning, some help message like "Your source is missing components referenced in your Package.xml file. Try using force:source:deploy /{file directory} like force:source:deploy /force-app" instead.

I think a more important issue is the sfdx does not intelligently handle things like flows well, whereas tools like force-cli and solenopsis determine how to only deploy missing / inactive flows.

from cli.

Why is there different behaviour when retrieving vs. deploying from the same package.xml? My (maybe naive) expectation is that if I have a component in my package.xml

1. it is pulled on retrieve (unless not existing, which is a package.xml error)
2. It is getting deployed on source:deploy (unless has a deployment problem)
   The behaviour should be consistent per metadata component imho

from cli.

@JimBTek Thank you for the feedback, we are tracking this bug in our internal system. Our internal work item is W-5749751, and I have it on our backlog for the summer release. I'll leave this ticket open till we fix it.

from cli.

Interesting thing I found: a typo in your deploy command can produce this error too.

sfdx force:source:deploy -m LightningtComponentBundle:myComponent

Note the extra "T" before "Component". This productes the same error described in the original post. Fixing the metadata name makes the command work.

Just commenting in case someone else has this same issue because of a silly typo. :)

from cli.

This issue has been linked to a new work item: W-9297987

from cli.