fork-ts-checker-webpack-plugin: Webpack fails with "Cannot find module /home/USER/PROJECT/--max-old-space-size=2048"

Had the exact same issue all of a sudden.

I was using serverless-bundle and used the following to fix it:

custom:
  bundle:
    disableForkTsChecker: true

as per https://www.npmjs.com/package/serverless-bundle

By default serverless-bundle uses the ForkTsCheckerWebpackPlugin to speed up builds by running type checking in a separate process. However, this combined with Serverless Framework’s package: individually: true option means that to packages each Lambda function, a separate type checking process is started. Concurrently, starting many such processes can cause your build process to run out of memory.

My serverless is added as a devDependency

also had to set memory limit to 4gb (memory hog nodejs)

NODE_OPTIONS=--max_old_space_size=4096 yarn deploy

I don’t have too much helpful to add here, but I am running into the same issue (new to serveless, webpack, etc. - following https://github.com/mtimbs/typescript-serverless and tracing the bug down to here) on macOS.

I have tracked down this line as a place where I can alter the behavior (i.e. by changing the memory limit the log changes its value). https://github.com/TypeStrong/fork-ts-checker-webpack-plugin/blob/5ba683960e871d387685379d5a78943e4a5dc679/src/rpc/rpc-ipc/RpcIpcMessagePort.ts#L112

This gets packaged up as

        this.service = childProcess.fork(path.resolve(__dirname, this.workersNumber > 1 ? './cluster.js' : './service.js'), [], {
            env,
            execArgv: (this.workersNumber > 1
                ? []
                : ['--max-old-space-size=' + this.memoryLimit]).concat(this.nodeArgs),
            stdio: ['inherit', 'inherit', 'inherit', 'ipc']
        });

Looks very similar to https://github.com/vercel/pkg/issues/909.

I have experienced the same thing, there were conflicting versions of serverless installed in two different locations. to figure out if you have the same issue run whereis serverless, if you are using nvm, remove the other one (~/.serverless/bin).

hmm… the comment that you cite is not correct, because RpcIpcMessagePort.ts file is from version >= 5, but

this.service = childProcess.fork(path.resolve(__dirname, this.workersNumber > 1 ? './cluster.js' : './service.js'), [], {
            env,
            execArgv: (this.workersNumber > 1
                ? []
                : ['--max-old-space-size=' + this.memoryLimit]).concat(this.nodeArgs),
            stdio: ['inherit', 'inherit', 'inherit', 'ipc']
        });

is a code from version 4. If serverless framework messes up with exec arguments, then I think it should be fixed there - not in this plugin. And based on the comments, it seems that the issue was fixed in newer versions of serverless so I would suggest upgrading 😃

Does not work for me even with local sls execution. I’m also using serverless-bundle

Serverless: Running "serverless" installed locally (in service node_modules)
^R
Serverless: DOTENV: Loading environment variables from :
Serverless: Bundling with Webpack...
Starting type checking service...
internal/modules/cjs/loader.js:967
  throw err;
  ^

Error: Cannot find module '/Users/david/Documents/GitHub/my-project/--max-old-space-size=2048'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:964:15)
    at Function.Module._resolveFilename (pkg/prelude/bootstrap.js:1346:46)
    at Function.Module._load (internal/modules/cjs/loader.js:840:27)
    at Function.Module.runMain (pkg/prelude/bootstrap.js:1375:12)
    at internal/main/run_main_module.js:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}```

Installing Serverless Framework via yarn global add serverless fixed the problem for me.

I had installed standalone on macOS. Moving to the npm version fixed this for me as well.

Had the same issue using standalone serverless binaries(1.80.0) and serverless-bundle(^3.0.0 using fork-ts-checker-webpack-plugin: ^4.0.1 ). Based on @hixus 's comment, I uninstalled the standalone version (originally installed via choco) and switched to the npm package npm install serverless -g and sure enough, that fixed it.

I have the same issue with global sls package. Although if I put sls as npm script and run npm run sls -- package there are no errors. Difference is:

sls --version Framework Core: 1.78.1 (standalone) Plugin: 3.7.0 SDK: 2.3.1 Components: 2.33.4

npm run sls – --version

Framework Core: 1.78.1 Plugin: 3.7.0 SDK: 2.3.1 Components: 2.34.1

If I try to update the global one it still says “Serverless: Already at latest version” even though the local Components are newer