fix!: remove child process option

README.md

@@ -137,7 +137,6 @@ All CLI options are optional:
 --printOutput               Turns on logging of your lambda outputs in the terminal.
 --reloadHandler             Reloads handler with each request.
 --resourceRoutes            Turns on loading of your HTTP proxy settings from serverless.yml
---useChildProcesses         [This option is deprecated] Run handlers in a child process.
 --useDocker                 Run handlers in a docker container.
 --useInProcess              Run handlers in the same process as 'serverless-offline'.
 --webSocketHardTimeout      Set WebSocket hard timeout in seconds to reproduce AWS limits (https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html#apigateway-execution-service-websocket-limits-table). Default: 7200 (2 hours)
@@ -188,15 +187,6 @@ Lambda handlers for the `node.js` runtime can run in different execution modes w
 - global state is being shared across lambda handlers as well as with `serverless` and `serverless-offline`
 - easy debugging
 
-#### child-processes
-
-- handlers run in a separate node.js instance
-- memory is not being shared between handlers, memory consumption is therefore higher
-- memory is being released when handlers reload or after usage
-- environment (process.env) is not being shared across handlers
-- global state is not being shared across handlers
-- debugging more complicated
-
 #### docker
 
 - handlers run in a docker container

src/config/commandOptions.js

@@ -130,11 +130,6 @@ export default {
     type: 'boolean',
     usage: 'Turns on loading of your HTTP proxy settings from serverless.yml.',
   },
-  useChildProcesses: {
-    type: 'boolean',
-    usage:
-      '[This option is deprecated] Use separate node process to run handlers.',
-  },
   useDocker: {
     type: 'boolean',
     usage: 'Uses docker for node/python/ruby/provided',

src/config/defaultOptions.js

@@ -29,7 +29,6 @@ export default {
   printOutput: false,
   reloadHandler: false,
   resourceRoutes: false,
-  useChildProcesses: false,
   useDocker: false,
   useInProcess: false,
   webSocketHardTimeout: 7200,

src/events/http/HttpServer.js

@@ -580,21 +580,8 @@ export default class HttpServer {
 
       // Failure handling
       let errorStatusCode = '502'
-      if (err) {
-        // Since the --useChildProcesses option loads the handler in
-        // a separate process and serverless-offline communicates with it
-        // over IPC, we are unable to catch JavaScript unhandledException errors
-        // when the handler code contains bad JavaScript. Instead, we "catch"
-        // it here and reply in the same way that we would have above when
-        // we lazy-load the non-IPC handler function.
-        if (this.#options.useChildProcesses && err.ipcException) {
-          return this.#reply502(
-            response,
-            `Error while loading ${functionKey}`,
-            err,
-          )
-        }
 
+      if (err) {
         const errorMessage = (err.message || err).toString()
 
         const found = errorMessage.match(/\[(\d{3})]/)

src/lambda/handler-runner/HandlerRunner.js

@@ -23,7 +23,7 @@ export default class HandlerRunner {
   }
 
   async #loadRunner() {
-    const { useChildProcesses, useDocker, useInProcess } = this.#options
+    const { useDocker, useInProcess } = this.#options
     const { handler, runtime } = this.#funOptions
 
     log.debug(`Loading handler... (${handler})`)
@@ -56,14 +56,6 @@ export default class HandlerRunner {
     }
 
     if (supportedNodejs.has(runtime)) {
-      if (useChildProcesses) {
-        const { default: ChildProcessRunner } = await import(
-          './child-process-runner/index.js'
-        )
-
-        return new ChildProcessRunner(this.#funOptions, this.#env)
-      }
-
       if (useInProcess) {
         const { default: InProcessRunner } = await import(
           './in-process-runner/index.js'