Aurel Drejta

Here is the whole stack that gets generated in clodwatch (lambda with node): ``` { "errorType": "Error", "errorMessage": "libc.musl-x86_64.so.1: cannot open shared object file: No such file or directory", "stack":...

I think the script is not running. I tried switching it to this: ``` custom: bundle: tsConfig: "tsconfig.json" copyFiles: - from: "./prisma/schema.prisma" to: "./" packagerOptions: scripts: - "cat > sample.txt"...

> Did you managed to get this working? Sadly I didn't. I had to switch to serverless-webpack plugin to get this working

No i replaced it with the serverless-webpack and am not using the serverless-bundle plugin at the moment. Sorry for not being clear about that. I do plan on revisiting this...

I came back to this and tried this setup with these configs: Node version : 14.0.0 serverless: 2.33.1 serverless-bundle: 3.0.0 Looks like prisma has to be added in to the...

@jayair The serverless-wepack plugin also had this issue and they fixed it by passing a concurrency number to limit the number of parallel packaging and type checking. Since serverless-bundle uses...

This might be related with serverless-webpack plugin since the logs ``` Serverless: Copy modules: /github/workspace/.webpack/login [3901 ms] Serverless: Prune: /github/workspace/.webpack/login [2810 ms] ``` are coming from the serverless-webpack package from...

Seems like if there are scripts that need to be run in the packagerOptions section then that is making the deployment process fail in github actions. ``` packagerOptions: scripts: -...

Thanks for the quick reply! Yes the method you proposed does work. I do understand that this bug is not really something critical since there seem to be other working...