Independent ESLint execution

We have a multi-module Maven project that has both Java and JavaScript (Vue.js) elements. We currently have an issue where a failure in the analysis of one of the three javascript projects results in none of the other projects being scanned.

The error we are seeing in the logs is as follows:

[DEBUG] 13:24:52.900 Skipping the start of eslint-bridge server as it failed to start during the first analysis or it’s not answering anymore

Obviously we need to fix the problem that is breaking the analysis of the first module (it’s incorrectly scanning a dependency and running out of memory), but is there a way to execute each JavaScript Module’s analysis in isolation so that a failure of one module doesn’t impact analysis of another?


1 Like