Resourcecrash
Could not start dependency X for resource Y
Also seen as: Could not start dependency dependency failed to start could not start dependency webpack for resource chat could not start dependency es_extended
What causes it
Resource Y depends on resource X, and X exists but FAILED to start — so Y can't start either. This differs from 'could not FIND dependency' (missing): here the dependency is present but erroring. The real problem is whatever made X fail, printed just above.
How to fix it
Fix the dependency (X) first — scroll up to find why X itself failed to start.
- Find resource X's own error, printed earlier in the console — that's the root cause.
- For a chain like esplugin_mysql → es_extended → esx_*, the FIRST resource to fail is the one to fix.
- Common root cause: a missing sub-dependency (e.g. fxmigrant, oxmysql) or a database issue.
- Fix X, then Y and the rest of the chain start normally.
Related errors
Related guides
Still stuck? We can help.
Optimized, dual-framework scripts for QBCore and ESX from Viper Development — escrow protected, delivered instantly to your Cfx portal.