-
Notifications
You must be signed in to change notification settings - Fork 99
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
Webpack modules not resolving #232
Comments
Internal SDK bug DCM-5025 has been filed. Thank you for the report. |
I'm still getting webpack error when building docusign-esign module. I tried that work around but didint work. Please let me know other options |
I'm having the same issue |
I'm having this issue as well. @EdwinMoralesDS , could you please provide a status update on internal SDK bug DCM-5025? |
Modifies lambda webpack config to deal with: docusign/docusign-esign-node-client#232
This issue is still happening more than a year after the last comment in the thread. @callumcox's suggestions work, but it's "hacky" due to other config changes needed to be made in order for everything to play nice. |
Hi,
We're using webpack, to minimize the size of the lambda we've got that consume the DocuSign client and I've had the same problem as #214. Digging into the src, looks like it's down to the AMD module resolution and the lack of preceding
./
in the require paths. Once I updated the modules inindex.js
with./
, these began resolving (until it encountered other imports in the models):An example of the error is below:
I dug around and found the following:
webpack/webpack#906
swagger-api/swagger-codegen#3336
https://webpack.js.org/loaders/imports-loader/
I've worked around it by installing imports-loader and adding the following into my webpack config:
Can the paths be updated to include the relative portion so the workaround isn't needed?
Thanks!
The text was updated successfully, but these errors were encountered: