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: explicitly import http
and https
modules due to bundler limitations
#2586
base: main
Are you sure you want to change the base?
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.
Ok, weird. Maybe some security issue?
Ohhh ok I finally got it 😅
I'll try to come up with a workaround, but yeah, it's not necessarily a bug with |
It's usually a problem with bundling. I'd reopen and merge this PR but add a comment that we need to explicitly import both modules due to some bundlers not being able to handle dynamic imports |
http
and https
modules due to bundler limitations
hm... yeah, avoiding the dynamic imports would make life easier for the bundlers, but this should also be fixed in |
Not all bundlers use rollup, we can't rely on it. This might become a non-issue anyway in future versions as we change the way requests are intercepted, I'd just revert to the previous behavior which was importing both modules statically |
Not sure why CI is failing though 😓 |
My CI broke because of a change in #2572
Some other people later mentioned this issue, but no one has yet found the root cause
Honestly I am curious but don't have the time to dig into it at this moment...