chore(deps): Bump IITM to ^2.0.1#18599
Conversation
| "cliui/wrap-ansi": "7.0.0", | ||
| "sucrase": "getsentry/sucrase#es2020-polyfills" | ||
| "sucrase": "getsentry/sucrase#es2020-polyfills", | ||
| "import-in-the-middle": "2.0.1" |
There was a problem hiding this comment.
We need this, else we get two IITM entries in the lock file
There was a problem hiding this comment.
I feel this backfire at some point
size-limit report 📦
|
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
| "cliui/wrap-ansi": "7.0.0", | ||
| "sucrase": "getsentry/sucrase#es2020-polyfills" | ||
| "sucrase": "getsentry/sucrase#es2020-polyfills", | ||
| "import-in-the-middle": "2.0.1" |
There was a problem hiding this comment.
I feel this backfire at some point
|
I was a little too late. But I post it for future references. Theoretically we don't have to update our package.json since we have a version range anyways. |
IITM has a new patch release with a fix that we need to properly instrument submodule imports in our Otel integrations (for instance to make this work).
Closes #18613