You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Got error when trying to install @webex/widgets #214
Hey folks. Thanks for reporting these issues and providing feedback. We'll get someone to look into this soon. @Kesari3008 do any of these errors seem familiar and similar to what we observed as we tried to upgrade our tooling?
Hey folks. Thanks for reporting these issues and providing feedback. We'll get someone to look into this soon. @Kesari3008 do any of these errors seem familiar and similar to what we observed as we tried to upgrade our tooling?
@sreenara Yes we have seen a similar error while upgrading our tooling but only once. Hence I cannot say for sure why it happens. One possible reason can be mismatch of React version as Widgets currently uses React 17. One way to resolve this is I remember that I installed querystring, crypto, os-browserify modules to resolve these polyfill errors. As a workaround, that's something which can be tried. In the meantime, I will check try this out to on my end again and find it's proper solution.
@Bhavik1363@Junior743@carrubbasamuel are you'll able to use React 17.x as a workaround for now? We will be working towards upgrading widgets to React 18 in the future.
Activity
Junior743 commentedon Oct 30, 2023
I have a similar problem, when a try to run: npx install-peerdeps @webex/widgets

I receive this result:
I think the problem is the react version. @webex/widgets are trying to install react 17, but I already using react 18.
And when I try to run: npm i @webex/widgets

I receive this result, and the react version error becomes more evident:
carrubbasamuel commentedon May 1, 2024
I have the same problem
sreenara commentedon Jul 9, 2024
Hey folks. Thanks for reporting these issues and providing feedback. We'll get someone to look into this soon.
@Kesari3008 do any of these errors seem familiar and similar to what we observed as we tried to upgrade our tooling?
Kesari3008 commentedon Jul 12, 2024
@sreenara Yes we have seen a similar error while upgrading our tooling but only once. Hence I cannot say for sure why it happens. One possible reason can be mismatch of React version as Widgets currently uses React 17. One way to resolve this is I remember that I installed querystring, crypto, os-browserify modules to resolve these polyfill errors. As a workaround, that's something which can be tried. In the meantime, I will check try this out to on my end again and find it's proper solution.
sreenara commentedon Jul 15, 2024
@Bhavik1363 @Junior743 @carrubbasamuel are you'll able to use React 17.x as a workaround for now? We will be working towards upgrading widgets to React 18 in the future.