'No MODULE named markup://c:name found' on an LWC deploy

Which module is missing from the target?

Your component quoteBanner has a line like import formatPrice from 'c/priceUtils'. At deploy time Salesforce looks for a module called priceUtils in the same namespace and does not find one. The bundle fails to compile, so it does not deploy.

The text in square brackets is the component that asked. The text before it is what it could not find. Together they give you the pair to check.

Why is the module missing?

• The child or utility module was never deployed. You shipped the parent only.
• The folder name and the import do not match. LWC folder names are camelCase, and c/priceUtils must match a folder called priceUtils exactly, including case.
• The module is a shared one you copied from somewhere else. The common case is c/pubsub: Salesforce does not ship a pubsub module out of the box, so you have to add it to your project and deploy it too (question 278714).
• The component sits in a managed package namespace, and the import uses c/ where it should use the package namespace.

What does the LWC error look like?

A bundle quoteBanner that imports c/priceUtils, which is not in the org. Check-only deploy:

quoteBanner (LightningComponentBundle)
No MODULE named markup://c:priceUtils found : [markup://c:quoteBanner]

In an org with a namespace, c shows as the namespace instead. The shape of the message is the same.

How do I fix it in Setup?

1. Look for the module in the target org. Setup > Custom Code > Lightning Components lists Aura and LWC bundles. In VS Code, run sf project retrieve start --metadata LightningComponentBundle:priceUtils -o <target-alias> to see if it exists.
2. If it is missing, add its folder to the deploy. Child modules and parents go in the same package.
3. If it exists under a different name, fix the import. Check the case on every letter.
4. Make sure the child bundle has its .js-meta.xml file. A folder without it does not deploy as a component.
5. Validate again.

How do I fix it with the CLI?

From the CLI, point at both folders in one call:

sf project deploy start --dry-run -o <target-alias> --source-dir force-app/main/default/lwc/priceUtils --source-dir force-app/main/default/lwc/quoteBanner

If the missing piece is Apex that the component imports with @salesforce/apex, you get a different message. The fix is the same: deploy the class first or in the same package.

How do I keep LWC imports in the same package?

Deploy LWC by folder tree, not by hand-picked files. When a component imports c/something, add something to the package in the same commit. Keep shared utilities in one folder and name them for what they do. One Stack Exchange question about this error is a child component that was left out of the deploy (question 383299).

Clientell AI's pre-flight checks cover deploy order and its diff is dependency-aware, so the parent and the modules it imports show up together. See AI Salesforce deployments. The Lightning web components glossary entry explains the model and the change set errors guide covers the same class of missing dependency.

Similar "no X named Y found" errors: missing field on a layout, missing quick action on a layout, missing grant in a profile or permission set, missing picklist value on a record type.