Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

eslint-plugin-react required? #69

Closed
donpdonp opened this issue Mar 17, 2015 · 3 comments

Comments

@donpdonp
Copy link

commented Mar 17, 2015

its not clear why this module would be necessary, or why its not in the pre-req modules if it is necessary.

$ npm install standard
npm WARN prefer global standard@3.1.1 should be installed with -g
standard@3.1.1 node_modules/standard

$ ./node_modules/.bin/standard api.js 
Error: Use JavaScript Standard Style (https://github.com/feross/standard)

Unexpected Linter Output:
module.js:340
    throw err;
          ^
Error: Cannot find module 'eslint-plugin-react'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
@maxogden

This comment has been minimized.

Copy link
Contributor

commented Mar 17, 2015

@donpdonp hmm its in the dependencies here https://github.com/feross/standard/blob/master/package.json#L19

maybe try installing standard again and seeing if that fixes it? might be an npm bug or something...

@donpdonp

This comment has been minimized.

Copy link
Author

commented Mar 17, 2015

I tried it in a project directory that had dozens of other npm packages installed. using standard from a clean directory appears to work fine. thx.

donp@wafer:~$ mkdir a
donp@wafer:~$ cd a
donp@wafer:~/a$ npm install standard
standard@3.1.1 node_modules/standard
├── get-stdin@4.0.1
...
donp@wafer:~/a$ touch blank.js
donp@wafer:~/a$ ./node_modules/.bin/standard blank.js 
donp@wafer:~/a$

@donpdonp donpdonp closed this Mar 17, 2015

@maxogden

This comment has been minimized.

Copy link
Contributor

commented Mar 17, 2015

I chalk this one up to npm gremlins, which are rarer than past days, but still lurk in the shadows from time to time

@lock lock bot locked as resolved and limited conversation to collaborators May 11, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants
You can’t perform that action at this time.