Closed 19Sean96 closed 1 year ago
Update:
I attempted the build on vercel.com and it does build successfully (which I suspected since NextJS is owned by them so it's highly optimized for that particular framework).
I suspect the failed build on Amplify could have to do with how NextJS parses packages during SSR, but I haven't had to really worry about that until today.
I'm going to attempt to use Webpack next to see if it has something to do with AMD parsing - which I wasn't familiar with until today. I suspect NextJS has this enabled by default - not entirely sure though.
@19Sean96 any luck? I'm experiencing the same issue here :(
Hi @19Sean96 Honestly, I haven't used AWS Amplify.
When amplify begins to run the SSR build process, it fails with exit code 1 due to not being able to resolve modules within the sib-api-v3-sdk/src directory.
I suspect the failed build on Amplify could have to do with how NextJS parses packages during SSR
. I can't think of any other explanation for the same.Thanks.
Since there is no response from the user for more than 11 days, I am closing this issue.
I do not submit issues often, so please let me know if I miss any information below and I'll happily provide what I can.
Package.json Info
Amplify.yml file:
Error Information:
next build
(oryarn run build
) on my local machine runs successfully.The problem When amplify begins to run the SSR build process, it fails with exit code 1 due to not being able to resolve modules within the
sib-api-v3-sdk/src
directory. Example:It seems all other modules within this package are also not being resolved, and I'm at a loss for words as to why this could be occuring. I will attach the build log file for further information.
log.txt