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
Setting up prettier-package-json #23
Comments
That’s to prevent you from accidentally overwriting all your files to empty files due to misconfiguration.
Side note: this config is too verbose. I opened #24 now that it’s possible |
Oh wait, I think I did that wrong. I’ll go over to my computer |
Ok, this is what you're going to want to do (don't use the
I just tested it out and it works for me. |
Thanks for looking at this right away. With out the --write flag I experience some weirdness. So much so, that I did a screen grab. The workspace package.json gets replaced with the content of the root level package.json. Same when I turn off stdin. Note that some of my term history shows errors from trying older versions of exec, but this recording uses 0.3.5. |
If I use pretty-package-json which supports stdin/out, things work as they should. |
Oh, I guess the plugin is not reading stdin. Providing the filepath seems to work and you can just ignore providing stdin since the plugin doesn't use it (I just checked its sourcecode):
Sorry, getting the config setup sometimes can be tricky, but afterwards it's not so bad |
No complaints here. I love it. Just stumbled (forgot all about {{file_path}} and stdin: false) and thank you for your help! |
Version: 0.34.5
I'm running prettier-package-json with the exec plugin. The associated files are formatted just fine but dprint exits with the error:
Entire config file attached, but heres exec:
Got something wrong with the config or a bug?
dprint.json.txt
The text was updated successfully, but these errors were encountered: