Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Webpack Formidable.js Bug?

  • 1.  Webpack Formidable.js Bug?

    Posted 06-05-2025 18:22

    xember | 2022-04-11 14:22:41 UTC | #1

    Hi,

    We are using "purecloud-platform-client-v2" library for nodejs (javascript) together with webpack. This used to work perfect (version 126.0.0) but since we upgraded to the latest version (134.0.1) the library doesn't seem to work in combination with webpack. After some debugging we can see that version 131.1.0 is still working but the version after that (132.0.0) is complaining:

    WARNING in ./nodemodules/formidable/src/Formidable.js 94:15-72 Critical dependency: the request of a dependency is an expression @ ./nodemodules/formidable/src/index.js 5:19-42 @ ./nodemodules/superagent/lib/node/index.js 48:17-38 @ ./nodemodules/purecloud-platform-client-v2/src/purecloud-platform-client-v2/ApiClient.js 1:0-36 110:20-30 281:17-27 537:16-26 939:18-28 @ ./node_modules/purecloud-platform-client-v2/src/purecloud-platform-client-v2/index.js 3:0-39 105:23-32 110:24-33 @ ./hello.js 3:0-58 43:4-52 44:4-52 46:20-43

    On the internet I found a solution for a previous version of formidable but that doesn`t seem to work:

    https://github.com/node-formidable/formidable/issues/337

    Beside this I can't imagine that Genesys is using such an old version :slight_smile:

    So I was wondering if somebody else has noticed this and hopefully there is a solution for this, otherwise how do I create a bug report?

    Thanks in advance,

    Best Regards,

    Peter

    anon11147534 | 2022-04-11 14:52:09 UTC | #2

    Hi Peter,

    We have recently updated the dependencies in our JavaScript SDK to the latest versions. Formidable is a dependency of superagent, we are using the latest version of superagent but they are using an old version of formidable (2.0.1 vs 3.1.4).

    We will look into this issue and release a fix for it. I'm not sure how to solve it at the moment, maybe we will have to revert to the old version of superagent that we were using.

    xember | 2022-04-11 15:00:09 UTC | #3

    Thanks for the quick response, we will revert to 131.1.0 and wait for the fix...

    system | 2022-05-12 15:00:55 UTC | #4

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 14277



Related Content