Error: Cannot find module 'eslint-config-standard-jsx' from ...

[chenxsan]

After updated standard to 6.0.1, I got this error:

I tested it on both Mac OSX and Windows 7.

But the module was installed under standard package:

I'm not sure what's going on here.

[matjaz]

+1
On node 4 I also get this error https://travis-ci.org/matjaz/stdin2/jobs/107404558
On node 5 it looks like a bug Expected parentheses around arrow function argument. https://travis-ci.org/matjaz/stdin2/jobs/107404555

[ungoldman]

I can confirm this error locally in node 4.x, 0.12, 0.10. Appears to work fine in 5.x. See https://travis-ci.org/ngoldman/module-init/jobs/107410146 for an example of the error recorded by travis-ci.

Possible causes:

• Shareable Config Changes in ESLint v2.0.0-rc.0
• differences between npm 2.x (ships with <=4) and 3.x (ships with >=5)

[ungoldman]

@matjaz I think it's working fine in node 5 in your case too: https://github.com/matjaz/stdin2/blob/master/test/index.js#L10

This is related to a rule change in standard 6:

Require parens in arrow function arguments
 (#309) (arrow-parens)

[ungoldman]

So as far as I can tell this passes in node 5 because 5 is bundled with npm 3, which installs eslint-config-standard-jsx in the root node_modules directory of the project. ESLint looks for the module in the root and everything is fine in that case.

In all non-bleeding-edge cases (npm@2.x), this is not fine, as the errors indicate.

Error: Cannot find module 'eslint-config-standard-jsx' from '/home/travis/build/matjaz/stdin2'
Error: Cannot find module 'eslint-config-standard-jsx' from '/Users/ng/dev/github/module-init'

I'm guessing this is an ESLint rc.0 bug creeping in with the new standard release. The .eslintrc in standard should be able to look for other modules to extend in the node_modules directory relative to its location in the dependency tree first, rather than going straight to the ${process.cwd()}/node_modules directory, failing, then giving up, right? Or something?

[chenxsan]

@ngoldman I'm using node 5.1.1 with npm 3.6.0.

[z0mt3c]

+1

[wraithan]

Node 5.5.0, tried with npm@latest and npm@2 both have the same issue. I'll give some other versions a shot if that would be valuable

[watson]

This seems to be an issue with version 2 of eslint where it uses process.cwd() to resolve plugins. I think this is also what's being discussed in eslint/eslint#5164.

I've tried to hack the current standard-engine codebase to overwrite the cwd temporarily and this seems to "fix" the problem (here is where it calls eslint)

[feross]

Sorry about this, everyone. This should be fixed in standard 6.0.3.

Thanks to everyone who helped debug this!

[feross]

I've opened an issue on eslint to try to fix the root cause of this issue: eslint/eslint#5175