The config param of the linter.verify() method doesn't support "extends" property

Tell us about your environment

• ESLint Version: 3.5.0
• Node Version: 6.5.0
• npm Version: 3.10.6

What parser (default, Babel-ESLint, etc.) are you using? default

Please show your full configuration:

{"extends": "eslint:recommended"}

What did you do? Please include the actual source code causing the issue.

const linter = require("eslint").linter;
const warnings = linter.verify("console.log();", {"extends": "eslint:recommended"});

What did you expect to happen? I expected linter.verify() to return an array with two warnings:

• Unexpected console statement (no-console)
• Newline required at end of file but not found (eol-last)

What actually happened? Please include the actual, raw output from ESLint. linter.verify() returned [] (an empty array)

[platinumazure]

Hi @EvgenyOrekhov, okay, then you want to use CLIEngine’s executeOnText() method to run the linter against your source text strings.

Here’s a rough idea of how you could do this:

const CLIEngine = require("eslint").CLIEngine;
const config = {"extends": "eslint:recommended"};
const sources = [
    "console.log('test');", // source code of a .js file
    "function myFunc() { ..." // source code of another .js file
];

cliEngine = new CLIEngine({
    baseConfig: config,
    useEslintrc: false   // Assuming that you don't want any .eslintrc in the filesystem to interfere. If you want .eslintrc, omit this
});

const warnings = sources.map((source) => cliEngine.executeOnText(source));

That should hopefully be very close to what you want. If you need to tweak the configuration options due to unexpected output or any other reason, take a good look at the many options that can be passed to the CLIEngine constructor.

Hope this helps-- if not, feel free to ask another question here or stop by on our Gitter chat.

[EvgenyOrekhov]

@platinumazure Thank you! Your suggestion solves my problem.