Library Instability


I am a software engineer at TELUS Digital (formerly WillowTree 🪦) and I am currently on a project where I’m building a mostly static public facing website. The tech stack is Astro with React with UnoCSS as a CSS framework, ContentStack as a CMS, Coveo as a search platform.

In only the last month or so, three of these (Coveo, UnoCSS, and ContentStack) have gotten updates which have broken our site in one way or another. These were patch or minor version updates which should not have caused a breaking change. In the case of UnoCSS, the break did not cause builds to fail, but styles no longer look the way they used to. In the case of Coveo and ContentStack, the issue was that the package authors do not apparently know how to make ESM compatible packages.

With the Coveo change I did enough investigating to find the actual commit that broke our project and discovered that it was made with a lengthy back-and-forth with an LLM GitHub agent. How many of our library dependencies are vibe-coded now and what will the long term effects of that be in terms of stability?