Esbuild Cache causing the serverless framework to stuck in limbo state

[arjun-deshta-toddleapp]

Context

We use serverless framework with esbuild for nodejs application

Problem Statement

When I am running serverless package for my application parallelly in Jenkins, the package process is getting stuck in a limbo state due the cache maintained by the esbuild, and at the end I had to manually terminate this pipeline or setup timeout.

Logs

[2026-02-13T11:22:59.467Z] Error:

[2026-02-13T11:22:59.467Z] Error: {"_tag":"SystemError","reason":"AlreadyExists","module":"FileSystem","method":"copy","pathOrDescriptor":"/home/ec2-user/workspace/cron/cron-staging/85/global-build/cron-ap-southeast-2/.esbuild/.build/node_modules/.bin/knex","syscall":"symlink","message":"EEXIST: file already exists, symlink '/home/ec2-user/workspace/cron/cron-staging/85/global-build/cron-ap-southeast-2/.esbuild/.build/node_modules/knex/bin/cli.js' -> '/tmp/ta-cron-1770981779432/node_modules/.bin/knex'"}

[2026-02-13T11:43:25.426Z] Sending interrupt signal to process

Can anyone help me, how can i resolve this issue or is there any feature which esbuild provides which i can use to get over this race condition due to common cache shared by all parallel builds