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

.prettierd file in $HOME #470

Open
christopher-lawrence opened this issue Jan 2, 2023 · 1 comment
Open

.prettierd file in $HOME #470

christopher-lawrence opened this issue Jan 2, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@christopher-lawrence
Copy link

My prettierd was not formatting correctly after the most recent change--v0.23.2. I checked the change log and noticed the new runtime folder location. I had a .prettierd in my $HOME folder, but it was a file, not a directory. Once I removed the file and restarted neovim everything worked as expected. The .prettierd directory was created and is being populated.

I'm not sure if this was my fault or if this is directly related to the recent changes with the location of the runtime files--I've been doing an overhaul on my neovim setup lately. Looking at the changelog I can not see where this file would have been created.

It might be worth adding a check to see if the .prettierd in $HOME is a folder and not a file.

@fsouza fsouza added the bug Something isn't working label Jan 2, 2023
@fsouza
Copy link
Owner

fsouza commented Jan 2, 2023

Hmm yeah that's a good point. I wonder if we should warn the user and ask them to kill older prettierd instances or simply remove the file.

Simply removing is bad because it'll leave a "zombie" prettierd process behind. Alternatively, we could change the configuration to use something like .prettier-data instead of the previous file name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants