Closed alexanderGugel closed 8 years ago
Nothing we can do about that.
This is not a bug in standard it's due to the issues surrounding symlinking and the expectation that symlinks aren't resolved when in fact require does resolve them.
No, this is due to the fact that eslint implicitly relies on npm's nested (even after v3) dependency graph to load shared configuration files.
Currently standard is not supported.
This is due to a reported bug in eslint: eslint/eslint#4263
The error will be along the lines of: