-
Notifications
You must be signed in to change notification settings - Fork 54
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
[BUG] Using Parcel to build/package generates a runtime TypeError #101
Comments
Thanks for bringing this to our attention @NVMKenneth, we're tracking this internally. |
@mhuynh5757 , do you guys have any update on this issue? I just ran into this problem too. We have just updated our React application to use Parcel 2 (we were using Parcel 1 before) and this problem came up. Is there any workaround to make it work, it any fix available? |
I also ran into this issue while building the Twilio Dev Phone. I ended up just writing my own webpack config, but it's definitely frustrating. https://stackoverflow.com/questions/71256281/a-constructor-from-a-node-module-im-importing-works-when-using-create-react-app/73736170#73736170 |
I forked the Twilio package and fixed it, but it looks more like a problem with Parcel and not Twilio, to be honest. |
@wsoaresfilho what was your solution? |
Please check #55 (comment) |
or sensitive account information (API keys, credentials, etc.) when reporting this issue.
Code to reproduce the issue:
Expected behavior:
Able to use Parcel as a build/packaging tool and have the SDK execute without TypeError. This error appears in a tab (not extension). The passed-in token and device values work fine.
Actual behavior:
When using parcel, I am getting a runtime TypeError. If using Webpack, this error does not appear.
Console log
Software versions:
The text was updated successfully, but these errors were encountered: