Closed stefjoosten closed 1 day ago
I'm going to close this for now. The solution seems to be a proxy that was inaccessible. It has been fixed, and I will type the analysis later so I can close this issue.
I think indeed that the warning you see last has nothing to do with the issue that it took so long. But you already mentioned that it was a proxy issue.
Furthermore, we are not maintaining the old frontend code anymore. So there won't be an update of the package lock unless really needed for existing use cases.
Btw, this clearly was an issue for the prototype repo.
What happened
I'm building a prototype in the cloud. When running composer, the build job does something strange. It starts waiting extremely long for 'supplemental metadata' because the package-lock.json file was created with an old version of npm:
Analysis
I'm clueless... Please comment with ideas of the cause of this problem...