Stuck at moveArtifactsToPackage during package cmd and Successfully published on deploy

[bkniffler]

I'm using serverless 2.39.0, also tried 2.38.0. Both package and deploy commands get stuck at the end and fail to exit the process without any clear error. Outputs are below and are with verbose+debug enabled.

Tried different configs, but it keeps on hanging on that moveToArtifactsToPackage step. Deploying still does work though, but the process will need to be cancelled with ctrl+c.

If I exchange serverless-esbuild with serverless-bundler, the process exits correctly.

Logs (package)

....
Serverless: Packaging service...
Serverless: Installing dependencies for custom CloudFormation resources...
Serverless: Invoke aws:package:finalize
Serverless: Invoke aws:common:moveArtifactsToPackage

Logs (deploy)

....
Serverless: Invoke aws:deploy:finalize
Serverless: Removing old service artifacts from S3...
Serverless: Publishing service to the Serverless Dashboard...
Serverless: Successfully published your service to the Serverless Dashboard: xxxx

Config

custom:
  esbuild:
    packager: npm
    bundle: true
    minify: false
    sourcemap: true
    target: node14
    watch:
      pattern: ['./index.ts', 'src/**/*.ts'] # default .
      ignore: ['.serverless/**/*', '.build'] # default ['.build', 'dist', 'node_modules']

Any idea what could be wrong?

[olup]

Hi ! Could you post your complete serverless.yml in order to get more context ?

[olup]

Actually I just updated to lastest serverless-esbuild and my deploys are also hanging. Will try to debug.

[olup]

Bug not happening in 1.10.4

[olup]

So It might be that we need to actively call result.rebuild.dispose() as we are now using incremental. Also, incremental build are only needed on offline mode (not with invoke or build or package)
https://esbuild.github.io/api/#incremental
in src/index.ts

[bkniffler]

Hey @olup, thanks for getting on this so quickly! I've downgraded to 1.10.4 and it works great :)

If there is anything you'd like me to attach, let me know, but looks like you found the cause already.

[olup]

yeah, I think so, thanks @bkniffler a lot for raising the error early, will revert once I have time to implement the fix

[github-actions]

🎉 This issue has been resolved in version 1.10.6 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀