Fork-ts-checker-webpack-plugin: No handler found for procedure getIssues

[jvvcn]

Current behavior

Hello guys, we are using typescript with the webpack setup & for type checking we decided to use fork-ts-checker-webpack-plugin and application is running within docker container. As far as we add new changes to the code I see the following in a logs

Steps to reproduce the issue

webpack config part related to fork-ts-checker-webpack-plugin

new ForkTsCheckerWebpackPlugin({
    eslint: { enabled: true, files: 'src', options: { extensions: ['ts', 'tsx'] } },
}),

...
{
  test: /\.ts?$/,
  exclude: /node_modules/,
  use: [{
     loader: require.resolve('babel-loader'),
     options: { plugins: [require.resolve('react-refresh/babel')] },
   }],
},

Dockerfile

FROM node:12-alpine
WORKDIR /app
COPY package.json yarn.lock ./
RUN yarn install
COPY . .
CMD ["yarn", "start"]

Environment

• fork-ts-checker-webpack-plugin: ^5.0.14
• typescript: ^3.9.7
• eslint: ^7.6.0
• webpack: ^4.44.1

[jvvcn]

Getting same error with same setup on a macOS, any ideas?

[piotr-oles]

Thanks for reporting this issue. Could you provide a reproduction repository?

[jsbroks]

I'm getting the same error, not really sure how to reproduce tho

[jvvcn]

@piotr-oles could it be due to lack of RAM for docker? Cuz I increased it up to 4 Gb and I don't have this error anymore

[piotr-oles]

That's may be the case. I have some logic to handle out-of-memory but maybe there is some edge-case when it doesn't work properly.

[rybkowskigrzegorz]

I have same issue, definitely it cannot be connected with lack of memory - tested on macOS 32GB RAM

[filippolcr]

Same issue with Nuxt 2.12 in Typescript with macOS Catalina 10.15.7

If additional infos are needed, I'm at your disposal.

ERROR  Error: No handler found for procedure getIssues.                 
15:06:56Error: No handler found for procedure getIssues.
    at Object.<anonymous> (/Users/******/Development/*****-website/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/RpcService.js:21:27)
    at Generator.next (<anonymous>)
    at /Users/******/Development/****-website/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/RpcService.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/Users/******/Development/****-website/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/RpcService.js:4:12)
    at callListener (/Users/******/Development/****-website/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/RpcService.js:16:39)
    at /Users/******/Development/****-website/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:31:13
    at Set.forEach (<anonymous>)
    at process.handleMessage (/Users/******/Development/****-website/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:30:26)
    at process.emit (node:events:376:20)

[Function: boundDispatch] [Function: boundCommit]                        15:06:59

[piotr-oles]

I was not able to reproduce it - if someone provides a reproduction repository, I will re-open this issue