This might help someone. I encountered an issue where an empty yarn.lock folder was being created during development builds, even though I’m using npm. Deleting this folder resolved the error for me.
2 Likes