Are binary targets still required for aws lambda?
# orm-help
m
Are binary targets still required for aws lambda?
To provide some context; all of a sudden having some really large generated files for serverless:
Copy code
97M	./prisma
 76M	./.prisma/client
 76M	./.prisma
 40M	./@prisma/sdk/dist/get-generators/engines/34df67547cf5598f5a6cd3eb45f14ee70c3fb86f
 40M	./@prisma/sdk/dist/get-generators/engines
 80M	./@prisma/sdk/dist/get-generators
121M	./@prisma/sdk/dist
122M	./@prisma/sdk
 89M	./@prisma/engines
230M	./@prisma
i can write a pattern to start excluding these things but what i am uncertain about is what MUST be there, because it does appear to be related to the issue https://github.com/prisma/prisma/issues/6932
Following the documentation at: https://www.prisma.io/docs/guides/deployment/deployment-guides/deploying-to-aws-lambda appears to state to add the following; which I think the sdk folder appears to be a devDependency as well:
Copy code
package:
  patterns:
    - '!node_modules/.prisma/client/libquery_engine-*'
    - 'node_modules/.prisma/client/libquery_engine-rhel-*'
    - '!node_modules/prisma/libquery_engine-*'
    - '!node_modules/@prisma/engines/**'