Opt-in to use included prettier version
See original GitHub issueHey 👋🏼,
If prettierd
doesn’t find a local version is falls back to the included version in this package. This is an issue in cases where a project doesn’t run prettier
and you introduce a lot of changes, which mainly is due to formatting.
I would argue that this is unwanted behavior and should not be the default but rather an opt-in option. What are your thoughts?
This is the only reason I’m currently using prettier_d_slim
instead of this project, but since my PR (https://github.com/mikew/prettier_d_slim/pull/11) never get merged I’d like to move over to this project and help out when I can.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Options - Prettier
Prettier ships with a handful of format options. To learn more about Prettier's stance on options – see the Option Philosophy. If you...
Read more >Install - Prettier
Note: If you forget to install Prettier first, npx will temporarily download the latest version. That's not a good idea when using Prettier, ......
Read more >Configuration File - Prettier
By default, Prettier automatically infers which parser to use based on the input file extension. Combined with overrides you can teach Prettier how...
Read more >CLI - Prettier
Use the prettier command to run Prettier from the command line. ... To run your locally installed version of Prettier, prefix the command...
Read more >Prettier 2.0 “2020”
And we've finally dropped support for Node versions older than 10, ... Prettier has included an option to configure trailing commas since ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sQVe opened #250 so you can have a look, we can also bikeshed on the name for the environment variable 😃
Will put off introducing a config file or flags for now, and will revisit if/when we get too many environment variables.
I think that’s a fair ask. Would you be ok with it being opt-out? I’m a bit worried with changing the default behavior and breaking other people’s workflow.