Prettier-vscode: Settings globally?

[kanlukasz]

So after Prettier 3 there is no option to use settings globally?
I don't like when something create additional files in my project folder 😥
Is there any solution to create one global file with Prettier settings?
Maybe somewhere in VSCode install folder?

[Ciantic]

This is bad for me too!

I've used global settings for years (?), and there is like ~60 or so projects that I don't want .prettierrc. Code I do is mostly throwaway WP garbage, with LESS and PHP and HTML, I don't want any of the .prettierrc files there because the prettier in that case is just a helper for myself.

Please, bring back the global settings.

Solution is to install 2.3.0, like this:

Then choose 2.3.0

[mrmokwa]

Solution is to install 2.3.0, like this:

...

Then choose 2.3.0

Thank you, this saved me

[ntotten]

You can set the prettier.configPath globally and point it to a shared configuration file. https://github.com/prettier/prettier-vscode#prettierconfigpath

[Ciantic]

@ntotten one more thing, if it's that easy, the little bubble suggest migrating should say it. The bubble gives an impression that you must now save it to all project directories individually, why else would other people were here too if it's just matter of setting single config.

So the thing is to do this:

Save the given .prettierrc e.g. to ~/.prettierrc, and then in VSCode settings.json:

    "prettier.configPath": "C:\\Users\\username\\.prettierrc",

[domvo]

You can set the prettier.configPath globally and point it to a shared configuration file.

This way it ignores project-based .prettierrc-files, which makes this solution useless imho. I need something like this:

1. Global settings
2. If there are local settings in a project, overwrite global settings

Basically exactly how it was done before.

[CiGit]

you can put a config file at the root of all your projects without using prettier.configPath (null)
/
...

• MyProjects
  
  
  
  • .prettierrc
  
  
  • ProjectA
  
  
  • ProjectB
  
  
  • Project with prettier
  
  
  • .prettierrc
  
  
  • ...
  
  

It can even be /.prettierrc I think

A config file is found from the file being processed and up the file system

This wouldn't work if your are developing inside a Container/VM/whatever :smile:

[kanlukasz]

"prettier.configPath": "c:\\Users\\xxxxx\\.vscode\\.prettierrc" works fine.
Thank you for advices

[cmckni3]

I removed my global settings from VS Code but now files that haven't been saved don't format using the settings from ~/.prettierrc.

[XiongAmao]

I removed my global settings from VS Code but now files that haven't been saved don't format using the settings from ~/.prettierrc.

@ntotten
Thx
I got the same problem. I didn't set any vscode prettier config in settings.json. , and ~/.prettierrc(i try~/.prettierrc.js/ ~/.prettierrc.config.js) doesn't work. It seems to be overwritten by the default vscode prettier config in 3.5.0.

When I format code manually:

https://github.com/prettier/prettier-vscode/issues/1049#issuecomment-553637060

Is the plan to keep the vscode configuration options or is the intention to remove that in the future?
Thx.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.