Remove plugin search feature

[fisker]

Description

Closes #14652
Closes #8056
Closes #9167
Closes #13583
Closes #8474

Checklist

• I’ve added tests to confirm my change works.
• (If changing the API or CLI) I’ve documented the changes I’ve made (in the docs/ directory).
• (If the change is user-facing) I’ve added my changes to changelog_unreleased/*/XXXX.md file following changelog_unreleased/TEMPLATE.md.
• I’ve read the contributing guidelines.

✨Try the playground for this PR✨

[sosukesuzuki]

I love changes like this that remove features as a maintainer, thank you. (One nits)

[fisker]

@kachkaev

Reply to your question in discord about "global installation".

I don't have a good answer for that, they'll have to run or alias prettier --plugin=prettier-plugin-foo or prettier --config=/path/to/global/.prettierrc.

[kachkaev]

@fisker maybe there could be some solution offered on the editor extension level. I believe that a global Prettier setup with plugins is mainly needed in somewhat non-standard environments like in education. For example, prettier-plugin-elm is used with litvis for teaching data visualisation:

3. Open a terminal window and install Prettier and Prettier Elm plugin with the following command:

   npm install --global prettier prettier-plugin-elm

In general, I am supportive of plugin search removal – this feature is really hard to implement for all package managers and various modes within them. We just need to be aware of us breaking certain valid use cases and be ready to offer a new solution for them. Perhaps, folks who do rely on global plugin search and can’t easily use import() in prettier.config.js can stick with v2 until a new solution is being sought. Once v3 is released, we’ll hear about more broken use cases which will help us finding something elegant. So let’s get this PR in! 🚀

[vinkla]

Is there a possibility that this pull request could resolve the hoisting issue in pnpm?

pnpm/pnpm#4700

[dangmai]

Hi,

I'm trying to understand the impact of this change for my plugin. Does this mean that I should ask all of my users to edit their Prettier config file to include something like:

{
  ... // rest of config
  "plugins": ["prettier-plugin-foo"]
}

or change their CLI call to include:

--plugin=prettier-plugin-foo

If that is the case, I can already foresee the amount of tickets opened in my project because of this 😭 .

I haven't followed upstream development closely recently, my assumption is that this will only be in Prettier v3 and above, not v2 right?

[fisker]

Correct.