Closed leppaott closed 8 months ago
[10.1.0] Reverts back to prettier 2.x by default due to issues with extension
[10.0.0] Use Prettier 3.0 by default. Change default configuration for trailingComma to all to match Prettier 3.0.
OK seems it could be by these changes? Prettier 2 works!
Can confirm this error.
same here
Seeing this same issue in latest plugin version. Downgrading to prettier 2 fixed it.
same here
Can confirm the issue
yup, same!
Removing prettierPath
from vscode settings fixed it for me (from https://github.com/n8n-io/n8n/pull/6952).
EDIT: No it didn't, now the extension ignores my config.
Removing
prettierPath
from vscode settings fixed it for me (from n8n-io/n8n#6952).
This worked for me too! Thanks for the suggestion. Hopefully this gets fixed asap...
Removing
prettierPath
from vscode settings fixed it for me (from n8n-io/n8n#6952).
Well I've missed that the extension now ignores my config, so its not really a fix :(
Have you all tried the workaround in #3100? That resolved this for me
Have you all tried the workaround in #3100? That resolved this for me This was the only fix that worked for me
After updating to 3.0, my project was throwing the same error. What fixed it for me was disabling/enabling the Prettier
extensions in VSC.
Removing the prettierPath
in the config did help me. Don't know whether it's reading the config (it seems weird that it wouldn't), but I did change it and then it did start working.
Removing prettierPath
config field from .prettierrc
worked for me. I have prettier 3.0.3
installed locally in my project.
Removing
prettierPath
from vscode settings fixed it for me (from n8n-io/n8n#6952).Well I've missed that the extension now ignores my config, so its not really a fix :(
Well, now it seems like it reads my config again, so the issue seems to be gone.
We haven't used prettierPath
but extension settings:
"prettier.configPath": "services/.prettierrc",
and we still got this.
Yeah I removed configPath
from settings.json
commited to repo and now the plugin formatting seems to work and also apply the prettierrc config.
Right this was only an issue with the path ./services/.prettierrc
works for me while before services/...
would work without ./
Restarting the vscode and removing the prettierPath
form the vscode settings worked for me
I restart VS Code, the problem goes away for a while, then comes back after some time, then I restart VS Code again each time it happens and I'm good for a while.
Something is up with it.
@leppaott can you please re-open this (but unsubscribe if you need)?
Still issue, .prettierrc is in root dir.
When I updated the prettier version in my project to 3.x.x, the formatting functionality didn't work, but when I updated the latest prettier plugin(vscode plugin), it worked fine.
I'm getting this error with Prettier 3.2.2
and Prettier VSCode Extension 10.1.0
. This is in a brand new project that uses a .prettierrc
in the root. In VSCode, I've tried specifying and not specifying where my .prettierrc
file is, with both absolute and relative paths.
somehow my prettier just accepted the .yaml format! .prettierrc.yaml https://prettier.io/docs/en/configuration.html
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.
Hello, we just updated Prettier to latest version 3 as well as
typescript
,jest
andts-jest
.After which formatting on test files stopped:
Also code files formatting doesn't work but sometimes it does. Does this extension use tsconfig or such?
Prettier config is on path
services/.prettierrc
and test files are onservices/module/__tests__/e2e/name.test.ts
and code onservices/module/src/...