-
Notifications
You must be signed in to change notification settings - Fork 821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Update import-in-the-middle
#4806
fix: Update import-in-the-middle
#4806
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thanks. I'll merge this in.
I think now we can now also consider changing the dependency to import-in-the-middle
to a caret range as many of the issues we were dealing with in previous versions are now resolved.
That would reduce the workload! Does iitm have tests that cover the things otel rely on? |
@timfish yes it does. The main reason we pinned it was nodejs/import-in-the-middle#57. @trentm added tests for it in nodejs/import-in-the-middle#66. @timfish feel free to open the PR to use a caret range, then I'll merge it in :) |
* fix: Update `import-in-the-middle` * add changelog entry * linting is important
import-in-the-middle
has had a few more bug fixes which have been released as v1.8.1 so I've bumper the version. This also included fixed types so no more type casting throughunknown
to get the types working!The v1.8.0 release has also been added to Github so I updated the previous changelog entry to point to that.