Replies: 1 comment 4 replies
-
|
Can you try the latest webpack version? Also can you provide reproducible test repo? |
Beta Was this translation helpful? Give feedback.
-
|
Apologies for the delay in reply. Here is the reproducible test repo |
Beta Was this translation helpful? Give feedback.
-
|
This is due to double bundling, I recommend to avoid it and put your code of |
Beta Was this translation helpful? Give feedback.
-
|
I am planning to publish the test-sdk as an npm package so I can't move the code to my application. Can I use the "externals" feature to avoid bundling the npm packages I have used in the sdk? Thanks again for your reply. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, you can, it is better solution for such cases |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I've created a JavaScript SDK (ABC) that uses the human library and tensorflow/tfjs for ML operations. I bundle the SDK using Webpack v5.94.
Everything works fine when I use the source code directly in my Next.js app using import { ABC } from "../../abc.js". However, when I install the SDK from npm (i.e., the bundled output), and then use import { ABC } from "@ABC/abc" I encounter the following error during the ML operations
The output type in the webpack config file is "module" and my package type is also "module" for both the SDK and my NextJS app.
Any ideas on what might be wrong with this setup?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions