Closed Pzixel closed 2 years ago
@Pzixel the easiest way would be to to just generate SDK to a src dir instead and don't use @dethcrypto/eth-sdk-client
. I am thinking about providing: https://github.com/dethcrypto/eth-sdk#outputpath
Another solution would be to copy all packages from the fat image:
./node_modules/@dethcrypto
./node_modules/.dethcrypto
<- this is where SDK is generated by default
Hi! I want to dockerize an app that uses
eth-sdk
but due to this magical process of placing generated types intonode_modules
I'm failing to do so.What I'm doing is building a multistage image to prevent
devDependencies
getting into resulting image. Here is my Dockerfile:The problem here is it's failing with cryptic errors:
I think some explanation about using
eth-sdk
in non-dev environment would be nice. I think I'm back to fat image with all development dependencies but I hope there is some solution for thisP.S. My package.json looks like this: