Hey @dbmikus,
This seems to be an issue with how we’re caching Node Modules for Workspaces. Currently, the Node Modules folder in your cache turns up to be empty. However, the next build believes that the cache has the files and thus, proceeds with that. Thus, it eventually fails.
This is already being discussed with our engineers as a few other users are seeing it too. We’ll let you know once we’ve more info.
Meanwhile, you’d have to continue deploying by clearing cache.