We’ve been trying to understand how Circle cache busting works in the context of node_modules.
Whenever we introduce a new dependency to our package.json (& npm-shrinkwrap.json), our build breaks for that branch and we must click “Rebuild without cache” on the branch build UI. We frequently have to do this again when this branch is merged into master.
This was much worse (completely unusable) when we were using bcrypt and other native C++ modules that required node-gyp to build.
I suspect we’re doing something wrong here, but am not sure what it is. Any help would be appreciated.