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

How to install plugin without issues? #287

Open
LeducH opened this issue Mar 4, 2021 · 5 comments
Open

How to install plugin without issues? #287

LeducH opened this issue Mar 4, 2021 · 5 comments

Comments

@LeducH
Copy link

LeducH commented Mar 4, 2021

Do you want to request a feature or report a bug?
BUG

What is the current/expected behavior?
I should be able to install the plug in without any issue but it throws a exception check further down

I use vimplug

Plug 'prettier/vim-prettier', { 'do': 'npm install' }

when I run :Prettier I get

Prettier: failed to parse buffer

What version of vim-prettier are you using - (output of :PrettierVersion) ?
1.0.0-beta

What version of prettier are you using - (output of :PrettierCliVersion) ?
2.2.1

What is your prettier executable path - (output of :PrettierCliPath) ?
prettier

Did this work in previous versions of vim-prettier and/or prettier ?
Maybe

thus is the error output

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/prettier
npm ERR!   prettier@"^2.0.4" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer prettier@"^1.15.0" from @prettier/[email protected]
npm ERR! node_modules/@prettier/plugin-php
npm ERR!   @prettier/plugin-php@"^0.11.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/user/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2021-03-04T15_32_17_641Z-debug.log

shell returned 1

@sizvix
Copy link

sizvix commented Mar 8, 2021

In package.json , delete the line with prettier/plugin-php if you don't need PHP
I works for me ;)

@LeducH
Copy link
Author

LeducH commented Mar 9, 2021

So you compile it yourself? I usually use vim-plug for install so how would I do this?

In either case it the issue remains.

laher pushed a commit to laher/vim-prettier that referenced this issue May 23, 2021
mitermayer added a commit that referenced this issue May 23, 2021
fix for #287: update dependency (prettier-php) to fix build
@laher
Copy link

laher commented May 28, 2021

@LeducH this has been fixed by a dependency upgrade - please can you verify and maybe close this

@ecohanim
Copy link

ecohanim commented Jun 3, 2024

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @prettier/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/prettier
npm ERR! prettier@"^3.0.3" from the root project
npm ERR! peer prettier@">=1.0.0" from @prettier/[email protected]
npm ERR! node_modules/@prettier/plugin-lua
npm ERR! @prettier/plugin-lua@"0.0.1" from the root project
npm ERR! 1 more (@prettier/plugin-xml)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer prettier@"^1.15.0 || ^2.0.0" from @prettier/[email protected]
npm ERR! node_modules/@prettier/plugin-php
npm ERR! @prettier/plugin-php@"^0.16.3" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/prettier
npm ERR! peer prettier@"^1.15.0 || ^2.0.0" from @prettier/[email protected]
npm ERR! node_modules/@prettier/plugin-php
npm ERR! @prettier/plugin-php@"^0.16.3" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

@msfukui
Copy link

msfukui commented Oct 10, 2024

I also encountered the same phenomenon.

The following pull request has been closed without being merged, but it seems that the issue will be resolved if it is merged. Could you please merge it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants