Possible environment issue introduced in v4.7.0 about atom-linter HOT 5 CLOSED

Hmmm, another failure that looks like it might be caused by v4.7.0: https://ci.appveyor.com/project/Arcanemagus/linter-phpcs/build/68

from atom-linter.

If I had to guess it's the long standing nodejs/node-v0.x-archive#2318
I'll be fixing this in sb-exec

from atom-linter.

Note to self: A similar work is done in linter-gsgl

from atom-linter.

A fix is up in steelbrain/exec#9
@Arcanemagus can you please confirm it fixes this?

from atom-linter.

As mentioned in AtomLinter/linter-php#152 (comment), it looks like:

We can fix the specs in packages by updating atom-linter from

export { exec, execNode } from 'sb-exec'

to

import { exec, execNode } from 'sb-exec'
export { exec, execNode }

from atom-linter.