Thanks Dan. I had just figured this out when I found your post. This had always worked for us on the Trusty container until yesterday, September 8th. I’m not sure when it broke, because as long as a cache exists the problem will be hidden. Perhaps CircleCI is no longer considering the presence of a
package.json sufficient reason to run
npm install? I’m not sure what the underlying cause is.
To CircleCI support: This hiccup and last week’s hiccup (where Composer stopped loading the designated PHP configuration file) have cost us hours of work. Some dev who isn’t in charge of keeping CircleCI running hits the problem, tries to determine if it is their fault, sends it to me. I have to stop what I’m doing, communicate to all devs that CircleCI is broken, troubleshoot it, commit a fix, everyone has to merge, and finally life can continue. Between different work schedules and time zones, project deliveries can get pushed back by an entire day or two due to one of these incidents. You are changing things far more often than you are mentioning in your changelog. Can you establish a beta-test set of users that will vet changes for problems before you roll them out to us?