I have a React 17 application where react-scripts was ejected to manually build Webpack config files. No rhyme or reason for that decision. At any rate, I cannot run on Node LTS because it generates the following error:
node:internal/process/promises:288 triggerUncaughtException(err, true /* fromPromise */); ^
RpcIpcMessagePortClosedError: Cannot send the message - the message port has been closed for the process 87196. ➜ frontend-user git:(issue_17) ✗ modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:47:47 at process.processTicksAndRejections (node:internal/process/task_queues:81:21) { code: undefined,
signal: undefined }Node.js v18.18.2
It is suggesting that the issue is a dependency called fork-ts-checker-webpack-plugin
✗ npm ls fork-ts-checker-webpack-plugin
[email protected] /Users/danielcortes/Projects/frontend-user
├── [email protected]
└─┬ [email protected] extraneous
└── [email protected] extraneous
Would upgrading to a newer version of this package resolve the error? What about just completely removing the package? It seems it just moves type checking to a separate process. Why would I need that? Typescript does type checking already.