Use the local XO when available

[sindresorhus]

Like the CLI does. Should have done this from the start. Can't remember why I didn't.

[novemberborn]

Can't remember why I didn't.

I suspect you may have to run the linting in a child process to prevent arbitrary packages from running within the Atom security context? (Don't know much about how that all works though.)

[sindresorhus]

@novemberborn There's a dirty workaround:

atom-linter-xo/index.js

Lines 11 to 13 in f3d443b

	allowUnsafeNewFunction(() => {
	lintText = require('xo').lintText;
	});

[novemberborn]

That avoids giving the dependency access to the Atom process?