Standard 10.0.0 stopped working when installed with pnpm

[zkochan]

Maybe this is something that should be fixed on the pnpm side, but I don't know what caused the issue, so maybe someone could help me to understand.

From version 10, if standard is installed using pnpm, when running standard, it throws these errors: Resolve error: unable to load resolver "node".

pnpm uses a different node_modules structure and bin files format but standard worked fine till v10. Can someone point me to what was changed that could break this?

[feross]

@zkochan What happens when you delete your node_modules and reinstall everything? Does that fix the issue?

Can you post the complete output from standard? This could be due to the new ESLint plugin we introduced: eslint-plugin-import

[zkochan]

Yes, I tried removing node_modules. However, with pnpm it is not really needed because it always creates the same node_modules structure.

Here's a repo to reproduce https://github.com/zkochan/pnpm-standard. I committed the whole node_modules folder.

When running npm t, it fails with this:

> pnpm-standard@1.0.0 test /home/zkochan/src/test/pnpm-standard
> standard

standard: Use JavaScript Standard Style (https://standardjs.com)
  /home/zkochan/src/test/pnpm-standard/index.js:1:1: Resolve error: unable to load resolver "node".
npm ERR! Test failed.  See above for more details.

[feross]

I'm really sorry but I don't have the bandwidth to debug this at the moment, so I'm going to close this issue to reflect that. If you (or someone else!) figure out how to fix this bug and have further information to share, or want to send a PR, I'm happy to take a look again.

[zkochan]

@feross I don't know what you did, but the issue has been fixed by standard@10.0.2. So thank you or anyone else who contributed the mysterious fix!

(the issue might have been a missing dependency. npm and yarn flatten dependencies, so frequently packages work even if someone forgets to add a dependency to package.json. Maybe I'll investigate what was the issue later)

[feross]

Glad it worked out for you!

[onlywei]

I'm currently experiencing this issue now in my own repository. Suddenly my eslint throws this same error message after switching to pnpm (I am not using standard). Let's see if I can investigate more details...

[zkochan]

@onlywei, feel free to file an issue in the pnpm repo

[onlywei]

@zkochan currently putting out some fires, so I temporarily removed the import/order rule from my .eslintrc.json. When I have more bandwidth I can investigate more to be able to provide more details for a better issue report.

[feross]

@onlywei Thanks for sharing. If you have additional info, that would be much appreciated.

[HeavenSky]

@feross @zkochan I found the same issue happend in standard@10.0.3 , but it really fixed in standard@10.0.2 ; below is my command log:

> standard --verbose|snazzy

standard: Use JavaScript Standard Style (https://standardjs.com)

\_\project\exec\npm\src\components\Menu.js
   1:1   error  Resolve error: unable to load resolver "node"  import/no-duplicates
  64:3   error  'componentWillReceiveProps' is not defined     no-undef
  67:3   error  'getArr' is not defined                        no-undef
  69:21  error  'arr' is not modified in this loop             no-unmodified-loop-condition
  74:3   error  'getKeys' is not defined                       no-undef
  81:3   error  'keySwitch' is not defined                     no-undef

\_\project\exec\npm\src\utils\fns.js
  3:3  error  Unexpected constant condition  no-constant-condition

\_\project\exec\npm\src\utils\global.js
  1:1  error  Resolve error: unable to load resolver "node"  import/no-duplicates

\_\project\exec\npm\src\view\index.js
  1:1  error  Resolve error: unable to load resolver "node"  import/no-duplicates

\_\project\exec\npm\src\view\root.js
  1:1  error  Resolve error: unable to load resolver "node"  import/no-duplicates

✖ 10 problems
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-antd@0.0.2 pre: `standard --verbose|snazzy`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-antd@0.0.2 pre script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.