RpcIpcMessagePortClosedError: Process 9160 exited with code "1"

[vocko]

Current behavior

I'm getting this error after upgrade to the latest version (6.4.0):

No issues found.
{absolutePathRemoved}\node_modules\typescript\lib\typescript.js:2559
            throw e;
            ^

Error: Debug Failure.
    at {absolutePathRemoved}\node_modules\typescript\lib\typescript.js:19596:89
    at String.replace (<anonymous>)
    at formatStringFromArgs ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:19596:21)
    at Object.createCompilerDiagnostic ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:19701:20)
    at tryReadFile ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:39904:23)
    at Object.getParsedCommandLineOfConfigFile ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:39852:30)
    at parseConfigFile ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:120744:43)
    at reloadConfigFile ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:120735:13)
    at updateProgram ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:120710:21)
    at updateProgramWithWatchStatus ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:120700:13)
{absolutePathRemoved}\node_modules\fork-ts-checker-webpack-plugin\lib\rpc\rpc-ipc\RpcIpcMessagePort.js:19
        closedError = new RpcIpcMessagePortClosedError_1.RpcIpcMessagePortClosedError(code
                      ^

RpcIpcMessagePortClosedError: Process 9160 exited with code "1" [null]
    at {absolutePathRemoved}\node_modules\fork-ts-checker-webpack-plugin\lib\rpc\rpc-ipc\RpcIpcMessagePort.js:19:23
    at Generator.next (<anonymous>)
    at {absolutePathRemoved}\node_modules\fork-ts-checker-webpack-plugin\lib\rpc\rpc-ipc\RpcIpcMessagePort.js:8:71
    at new Promise (<anonymous>)
    at __awaiter ({absolutePathRemoved}\node_modules\fork-ts-checker-webpack-plugin\lib\rpc\rpc-ipc\RpcIpcMessagePort.js:4:12)
    at ChildProcess.handleExit ({absolutePathRemoved}\node_modules\fork-ts-checker-webpack-plugin\lib\rpc\rpc-ipc\RpcIpcMessagePort.js:18:42)
    at ChildProcess.emit (node:events:394:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
  code: 1,
  signal: null
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Build finishes fine, seems that even the checking as per the "No issues found" line, but then I get this error and the dev server process crashes. Any ideas what can be wrong?

Expected behavior

The previous version 6.3.4 was running fine with no issues (on the same codebase). I have even verified by reverting the yarn upgrade changes in git and running the same command. Works just fine, it must be some change between the 6.3.4 and 6.4.0.

Steps to reproduce the issue

Just running yarn start what runs webpack serve --config webpack.config.development.js

Issue reproduction repository

Environment

devDependencies
(all I thought they might be possibly related)
"@typescript-eslint/parser": "^5.4.0",
"eslint": "^8.2.0",
"eslint-import-resolver-webpack": "^0.13.2",
"eslint-plugin-flowtype": "^8.0.3",
"eslint-plugin-import": "^2.25.3",
"eslint-plugin-jsx-a11y": "^6.5.1",
"eslint-plugin-react": "^7.27.0",
"fork-ts-checker-webpack-plugin": "^6.4.0",
"ts-loader": "^9.2.6",
"typescript": "^4.5.2",
"webpack": "^5.64.1",
"webpack-cli": "^4.9.1",
"webpack-dev-server": "^4.5.0"

• os: Windows 10
• Yarn: 1.22.5

[piotr-oles]

Hi! Thanks for reporting this issue. Could you create a reproduction repository?

[vocko]

Hi Piotr,
thank you for a quick reaction. I will try to put some sample together. The project where it is happening is a little too big, but let's see if I can reproduce it on some extract.

[vocko]

I have tried to reproduce on react-start-app sample, but not successful at least not yet. Even when using the same webpack.config.js, package.json and tsconfig.json. I was also trying to switch between babel-loader and ts-loader but without any effect. I have tried to increase the memory limit and get more logging, but did not give me much light.

I have also tried to set typescript mode parameter to write-references but got the same result.

I don't understand much how all this works under the hood so any help will be appreciated, however, I understand that without reproducible example it might be hard to figure this out.

new ForkTsCheckerWebpackPlugin({
            typescript: {
                memoryLimit: 4096,
                mode: 'write-references'
            },
            logger: {
                infrastructure: 'console',
                issues: 'console',
                devServer: true
            }
        })

Here is my tsconfig.json, if anyone would spot something obviously wrong, but I don't think that's the case.

{
  "compilerOptions": {
    "allowJs": true,
    "allowSyntheticDefaultImports": true,
    "allowUnreachableCode": false,
    "baseUrl": "./src",
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "module": "esnext",
    "moduleResolution": "node",
    "outDir": "./dist/",
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "react",
    "lib": [
      "es2017",
      "ES2015.Promise",
      "dom"
    ],
    "removeComments": true,
    "resolveJsonModule": true,
    "skipLibCheck": false,
    "strict": true,
    "target": "es2017"
  },
  "include": [
    "src/*"
  ]
}

webpack.config.js looks like this

'use strict';

const path = require('path');
const HtmlWebPackPlugin = require('html-webpack-plugin');
const ForkTsCheckerWebpackPlugin = require('fork-ts-checker-webpack-plugin');
const PUBLIC_PATH = path.resolve(__dirname, 'build');

module.exports = {

    entry: {
        app: './src/index.tsx',
    },
    output: {
        path: PUBLIC_PATH,
        filename: '[name].[contenthash].js',
    },

    resolve: {
        extensions: ['.ts', '.tsx', '.js', '.jsx', '.css', '.scss'],
        fallback: { "stream": false }
    },

    target: 'web',

    mode: 'development',

    devtool: 'eval-source-map',

    devServer: {
        devMiddleware: {
            publicPath: '/',
            index: './index.html'
        },
        static: {
            directory: path.resolve(__dirname, './')
        },
        historyApiFallback: true,
        port: 3000,
        hot: true,
        allowedHosts: [
            'localhost'
        ]
    },

    module: {
        rules: [
            {
                test: /\.(ts|js)x?$/,
                exclude: /node_modules/,
                use: [
                    {
                        loader: 'babel-loader'
                    }
                ]
            },
            {
                test: /\.(s[ac]ss|css)$/,
                use: [
                    {
                        loader: 'style-loader',
                    },
                    {
                        loader: 'css-loader',
                        options: {
                            modules: {
                                localIdentName: '[name]_[local]_[hash:base64:6]',
                                exportLocalsConvention: 'camelCase',
                            },
                            importLoaders: 2,
                            sourceMap: true
                        }
                    },
                    {
                        loader: 'sass-loader',
                        options: {
                            implementation: require('sass'),
                            sourceMap: true
                        },
                    }
                ]
            },
            {
                // Generates a react component wrapping an SVG
                test: /\.svg$/,
                use: [
                    {
                        loader: 'babel-loader'
                    },
                    {
                        loader: '@svgr/webpack',
                        options: {
                            babel: false,
                            dimensions: false,
                            typescript: true,
                            ext: 'tsx',
                            svgoConfig: {
                                plugins: [{
                                    prefixIds: {
                                        prefixIds: false,
                                        prefixClassNames: false
                                    }
                                }]
                            },
                            template: (
                                { template },
                                opts,
                                { imports, componentName, props, jsx, exports }
                            ) => {
                                const typescriptTemplate = template.smart({
                                    plugins: ['typescript'],
                                });

                                // Custom template to allow apply custom colours to an svg from an object
                                // "id" and "data-theme" properties must be set in order to apply the theme
                                // Theme object structure is { primaryColor: '#color', secondaryColor: '#color'}
                                return typescriptTemplate.ast`
                                  ${imports}
                                  const ${componentName}: React.FC<React.SVGProps<SVGSVGElement>> = (props) => ${jsx}
                                  ${exports}
                                `
                            }
                        }
                    },
                ]
            }
        ],
    },
     plugins: [
        new ForkTsCheckerWebpackPlugin(),
        new HtmlWebPackPlugin({
            template: imports.path.resolve(__dirname, 'src/index.ejs'),
            filename: './index.html'
        })
     ]
};

I have also seen this issue which seems similar to mine, but might not be related: #630

[piotr-oles]

It seems like there is some issue in readFile call in typescript. It's related to this function:

(it may be slightly different on your project - I don't know your exact typescript version)

So you can search for this function in node_modules/typescript/lib/typescript.js file and add a few console.logs, for example, console.log(fileName, e); in the catch block.

[vocko]

It occurs with the latest 4.5.2, but I think I had the same issue with some older version too. I will try to log the function you've said tomorrow and will let you know if I get any usable information out of it.

Thank you for looking into it!

[vocko]

So I have added this logging line:

function tryReadFile(fileName, readFile) {
    var text;
    try {
        text = readFile(fileName);
    }
    catch (e) {
	console.debug(e, fileName, readFile);
        return ts.createCompilerDiagnostic(ts.Diagnostics.Cannot_read_file_0_Colon_1, fileName, e.message);
    }
    console.debug(fileName, text);
    return text === undefined ? ts.createCompilerDiagnostic(ts.Diagnostics.Cannot_read_file_0, fileName) : text;
}

on got this:

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
    at new NodeError (node:internal/errors:371:5)
    at validateString (node:internal/validators:119:11)
    at Object.normalize (node:path:305:5)
    at normalizePath ({absolutePathRemoved}\node_modules\fork-ts-checker-webpack-plugin\lib\typescript-reporter\file-system\RealFileSystem.js:21:39)
    at getRealPath ({absolutePathRemoved}\node_modules\fork-ts-checker-webpack-plugin\lib\typescript-reporter\file-system\RealFileSystem.js:67:32)
    at Object.realPath ({absolutePathRemoved}\node_modules\fork-ts-checker-webpack-plugin\lib\typescript-reporter\file-system\RealFileSystem.js:153:20)
    at Object.readFile ({absolutePathRemoved}\node_modules\fork-ts-checker-webpack-plugin\lib\typescript-reporter\file-system\PassiveFileSystem.js:53:44)
    at Object.readFile ({absolutePathRemoved}\node_modules\fork-ts-checker-webpack-plugin\lib\typescript-reporter\reporter\ControlledTypeScriptSystem.js:129:44)
    at Object.readFile ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:116517:68)
    at {absolutePathRemoved}\node_modules\typescript\lib\typescript.js:39852:92 {
  code: 'ERR_INVALID_ARG_TYPE'
}
undefined
[Function (anonymous)]

And here is the stack trace for the error:

Trace
    at tryReadFile ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:39907:12)
    at Object.getParsedCommandLineOfConfigFile ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:39853:24)
    at parseConfigFile ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:120750:43)
    at reloadConfigFile ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:120741:13)
    at updateProgram ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:120716:21)
    at updateProgramWithWatchStatus ({absolutePathRemoved}\node_modules\typescript\lib\typescript.js:120706:13)
    at Immediate._onImmediate ({absolutePathRemoved}\node_modules\fork-ts-checker-webpack-plugin\lib\typescript-reporter\reporter\ControlledTypeScriptSystem.js:178:17)
    at processImmediate (node:internal/timers:464:21)

Does it give any idea?

As I have said above, it seems it does all the compilation and checking fine and fails after all that is done.

Also, I did try to add the debugging to my last working version and it doesn't seem to make the call at all. When I upgrade the libraries, it seems to do the check twice and fails after the second round. Not sure whether that's an issue with my configuration anywhere, but I have only reverted package.json and yarn.lock, ran yarn install and yarn start and it all went through fine.

These are the libs that work:

"@babel/core": "^7.15.0",
"@babel/preset-env": "^7.15.0",
"@babel/preset-react": "^7.14.5",
"@babel/preset-typescript": "^7.15.0",
"babel-loader": "^8.1.0",
"fork-ts-checker-webpack-plugin": "^6.3.4",
"typescript": "^4.4.4",
"webpack": "^5.58.2",
"webpack-cli": "^4.9.0",
"webpack-dev-server": "^4.3.1"

[piotr-oles]

Could you try to add these lines of code to the
node_modules/fork-ts-checker-webpack-plugin/lib/typescript-reporter/reporter/ControlledTypeScriptSystem.js file
and check if it solves the issue?

[vocko]

Hi Piotr,

this is really annoying now, but I had to revert the libraries to the last working version yesterday as I needed to do some other stuff and once upgraded back to the latest, the issue has disappeared and I can't reproduce it anymore. Possibly any race condition?

I have tried both yarn upgrade and yarn upgrade --latest but not successful, the checker seems to behave correctly suddenly. I think we can close this issue for now, I will reopen it later if I manage to reproduce the problem again. Also will try apply your fix in that case.

Sorry for taking your time, really appreciated for looking into this.

[piotr-oles]

No problem, I'm glad that the problem is solved :)

[ghiscoding]

I have pretty much the same problem, it keeps crashing on my local and I tried to revert to previous TypeScript version (instead of latest) but that didn't help. It happens quite often, not sure if it's specific to a computer or not yet, but I get this error (nearly the same error as described)

closedError = new RpcIpcMessagePortClosedError_1.RpcIpcMessagePortClosedError(code
                      ^
RpcIpcMessagePortClosedError: Process 9108 exited with code "1" [null]

I'm on Windows and I need to go and kill all left open NodeJS thread every time it crashes. I also recently switch to esbuild-loader instead of ts-loader but I'm not sure if that could be the cause yet either.

My project Open Source and is kinda large since it's a monorepo but if it helps, it's available here: Slickgrid-Universal and you can look at my webpack.config.js

[vocko]

@ghiscoding Could you try to apply the fix what Piotr posted above? I wanted to test that but the issue somehow miraculously vanished from my solution and I suddenly can't reproduce it anymore.

[ghiscoding]

@vocko @piotr-oles
That patch seems to help, it didn't crash since I updated the code, so it would probably be a good idea to create a PR with this fix.