Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
sara81
3 years agoHelpful | Level 5
Can't resolve './aes' error when using @dropbox/sign
Node: 18.17.1
@dropbox/sign: 1.1.3
Hi,
when I try to use the sdk I get the following error:
- error ./node_modules/@dropbox/sign/dist/api.js
Module not found: Can't resolve './aes'
The error comes from this simple piece of code:
import * as DropboxSign from '@dropbox/sign';
const signatureRequestApi = new DropboxSign.SignatureRequestApi();
Would be very greatful for any help on this.
Best,
S
10 Replies
- DB-Des3 years ago
Dropbox Community Moderator
There was an issue opened in GitHub recently, which prompted one of our engineers to create a sample repo for how Dropbox Sign SDK can be implemented using Next.js.
- sara813 years agoHelpful | Level 5
Have your team created an issue for Next.js that I can follow?
Thanks for the workaround! I think I can make it work for now but would be great to remove the workaround/hack at some point of time.
- reef8783 years agoExplorer | Level 4
this is very helpful, thank you! i'll use the method you've proposed for now.
- Juan - Dropbox3 years ago
Dropbox Staff
Hi there. I've created an example repo for anyone using Next.js + the Sign Node SDK: https://github.com/hellosign/nextjs-blog
The trick is next.config.js must ignore fs and axios on client-side rendering.
Make sure to invoke the SDK package only within getStaticProps or getServerSideProps functions.
Unfortunately per my response in this GitHub issue I don't know Next.js well enough to figure out how to make the above work when using its App Router - so the solution will only apply if you are not using it.
- reef8783 years agoExplorer | Level 4
thank you for the response! i created this github issue and am hoping it helps myself & anyone else who might be facing this issue with the package.
- DB-Des3 years ago
Dropbox Community Moderator
Hi,
We have not received any reported issues from developers who have been using the Node SDK since its official release.
You can reach out to our support team with more details, including code snippets, for your integration to see if we can figure out where the error is coming from.
- reef8783 years agoExplorer | Level 4
this doesn't solve the problem--i'm hitting the exact same issue & i've reviewed all the referenced documentation. is there possibly an issue with the package itself?
- DB-Des3 years ago
Dropbox Community Moderator
Hello,
The reason you are seeing that error is because the Dropbox Sign Node SDK uses Node.js specific modules, or modules that are not available on the client side.
You can address that issue by looking into NextJS'
getStaticProps,getStaticPathsorgetServerSidePropsfunctions.References:
Hope this helps!
- sara813 years agoHelpful | Level 5
Hi,
to answer your questions.
1) I am using npm 9.6.7
2) I'm triggering this code from an api route in Next.js.3) I'm using Next.js 13.4.19
FYI: I got the same behavior using node 20 as 18. - DB-Des3 years ago
Dropbox Community Moderator
Hi there,
Just a few questions, for you:
- Did you install the DropboxSign API using npm?
- Are you using a front-end library, such as React?
- Are you using a framework such as Vue or NextJS?
About Dropbox Sign API
The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.
If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X, Facebook or Instagram.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!