I’ve browsed the EsLint docs hoping to find an option to configure it to run with more memory. Sadly I was not able to find anything of the sort.
However, inspired by @vsemozhetbyt’s answer -hence the up-vote- I started looking at Node’s configuration options and I’ve found a way to get around this using Node’s NODE_OPTIONS environment variable.
A space-separated list of command line options. options… are interpreted as if they had been specified on the command line before the actual command line
So this is what I did:
$ export NODE_OPTIONS="--max-old-space-size=4096"
$ echo $NODE_OPTIONS
--max-old-space-size=4096
$ eslint app.js
This way the Node process that runs EsLint just picks this up without the need for me to type in the --max-old-space-size flag nor the path to the Node binary every time I invoke EsLint.