Running serverless-offline with serverless-esbuild using NODE_OPTIONS="--trace-warnings" serverless offline start leads to the following behavior during development:
Whenever a file is updated my machine freezes and I get the following warning:
(node:38275) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 exit listeners added to [Worker]. Use emitter.setMaxListeners() to increase limit
at _addListener (node:events:591:17)
at Worker.addListener (node:events:609:10)
at Worker.once (node:events:653:8)
at node:internal/worker:377:12
at new Promise (<anonymous>)
at Worker.terminate (node:internal/worker:376:12)
at WorkerThreadRunner.cleanup (file:///repository/node_modules/serverless-offline/src/lambda/handler-runner/worker-thread-runner/WorkerThreadRunner.js:30:31)
at HandlerRunner.cleanup (file:///repository/node_modules/serverless-offline/src/lambda/handler-runner/HandlerRunner.js:105:25)
at LambdaFunction.cleanup (file:///repository/node_modules/serverless-offline/src/lambda/LambdaFunction.js:220:31)
at file:///repository/node_modules/serverless-offline/src/lambda/LambdaFunctionPool.js:63:41
at Set.forEach (<anonymous>)
at file:///repository/node_modules/serverless-offline/src/lambda/LambdaFunctionPool.js:62:23
at Map.forEach (<anonymous>)
at #cleanupPool (file:///repository/node_modules/serverless-offline/src/lambda/LambdaFunctionPool.js:61:16)
at LambdaFunctionPool.cleanup (file:///repository/node_modules/serverless-offline/src/lambda/LambdaFunctionPool.js:76:28)
at Lambda.cleanup (file:///repository/node_modules/serverless-offline/src/lambda/Lambda.js:66:37)
at #cleanupFunctions (file:///repository/node_modules/serverless-offline/src/ServerlessOffline.js:142:26)
at PluginManager.runHooks (/repository/node_modules/serverless/lib/classes/plugin-manager.js:530:15)
at PluginManager.invoke (/repository/node_modules/serverless/lib/classes/plugin-manager.js:564:20)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async PluginManager.spawn (/repository/node_modules/serverless/lib/classes/plugin-manager.js:585:5)
Bug Report
Current Behavior
Running
serverless-offline
withserverless-esbuild
usingNODE_OPTIONS="--trace-warnings" serverless offline start
leads to the following behavior during development:Whenever a file is updated my machine freezes and I get the following warning:
Sample Code
Expected behavior/code
I wouldn't expect to see this warning. My machine shouldn't freeze every time I hit save.
Environment
serverless
version: v3.35.2serverless-offline
version: v13.2.0node.js
version: v18.18.0OS
: macOS 13.0.1pnpm
: v8.9.0I'm using PNPM with workspaces and Turborepo.