Resource depends on something that is not installed

What the console says

Could not find dependency <dep> for resource <resource>
Failed to load script … <resource>

What it means

<resource> requires <dep>, which is not installed or not started.

How to fix it

1. Install the dependency, or remove the resource.
2. Check the dependency has not been silently pulled from its source — vendors delist assets.

When it is not this

A resource that fails to start is NOT automatically broken - it can be stopped ON PURPOSE. Real example: a server keeps esx_multicharacter INSTALLED BUT NOT RUNNING because a different multicharacter resource (0resmon) reads the character data esx_multicharacter stores; leaving its dependency unmet is precisely how it is kept installed-but-stopped. Reporting that as a fault every restart is how a monitoring tool gets muted. ALWAYS ask whether the state is intended before escalating, and once an owner confirms it is deliberate, record it as a per-server acknowledgement so it is never raised again. Separately: Node build tools listed as FiveM dependencies are bogus and WILL block startup - 'webpack' and 'yarn' in an fxmanifest are not resources. fxmanifest.lua is plaintext-editable even in escrow.