No, based on my understanding of the eslint documentation, and my reading of the current source of apigeelint, the plugin for eslint does not support external configuration! I am surprised. That's an unfortunate limitation.
I am not completely certain of this, because the documentation of the eslint npm module is not quite as clear as I would like. The current code of apigeelint passes a hardcoded set of rules to the linter. What I am uncertain about is, does the eslint.Linter object implicitly scan for an .eslintrc file and apply its rules? I suppose it would be easy to test.
If the eslint.Linter object does not implicitly read .eslintrc files, I think it would not be too difficult to extend apigeelint to read an .eslintrc file that you specify, somehow. Maybe apigeelint should automatically look for .eslintrc in the root of the bundle. Would that work for your purposes? Let me ask something different: how would you like to specify the eslint rules? If we find that its necessary, I can work on a Pull request that would extend it to support externally-specified rules.
One [lame] workaround: you can specify in-line rules, within the JS code. This is ok for small codebases, but obviously is tedious and wrong for the case where you have lots of files to analyze.
LinkedIn
Twitter
