Vercel: Build Cache keeps the old result after the dependencies change
Preview shows the previous version of the library despite changes in the code.
How to identify the source of the problem
Compare SHA lockfile and installation log with the current commit to deployment.
Compare SHA commit, the status of deployment and HTTP response under the final domain, not the very status of READY.
Repair steps
Perform redeploy without cache after determining the cause and make sure the package-lock is up-to-date.
How to Test Solution
The new build contains the right package and the next defloye does not play the old configuration.
Security and restrictions
Keep the previous active deployment until the new one is confirmed under your own domain. Avoid writing secrets in logs.