What is the best way for us to identify breaking changes in a minor version upgrade? Attempted an upgrade and got initialization failures
u
Uday
01/02/2026, 4:55 AM
Hey @Chad Holmes, you can keep an eye on our changelog: https://docs.composio.dev/docs/changelog.
Also, could you share more details on the issue you are facing so we can help you out? Thanks!
c
Chad Holmes
01/02/2026, 5:13 PM
ECS containers are crashing and it appears it was due to a newly introduced bunlding issue
Chad Holmes
01/02/2026, 5:13 PM
My investigation so far:
The issue was in @composio/core/dist/chunk-SfbczIpV.mjs:
var __require = /* @__PURE__ */ createRequire(import.meta.url);
This is in the ESM chunk file from @composio/core. When esbuild bundles this ESM file into CJS,
it converts import.meta to an empty object {}, causing import.meta.url to be undefined.
u
Uday
01/02/2026, 5:18 PM
Thanks for flagging this! I've escalated it to the eng team and I'll keep you updated.
c
Chad Holmes
01/02/2026, 5:26 PM
I think It will work if I bundle as external, trying that now. Appreciate the quick repsonse here though
Chad Holmes
01/02/2026, 5:44 PM
Yeah adding this in our esbuild command worked
--external:@composio/client --external:@composio/core