Use global `prettier` package as a fallback when Prettier is not installed inside a project.
See original GitHub issueWhen inside a directory with a package.json
that has prettier
as a dependency, this extension will not format a document until I run yarn install
(or npm install
), even if I have prettier
installed globally on the machine. Seems like the extension should check for a global fallback rather than just failing.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
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 >In VS Code, I'm getting this error, 'Failed to load module ...
A workaround is to remove the prettier entry in package.json of this package - no local/global prettier install necessary.
Read more >failed to load prettier from package.json · Issue #1066 - GitHub
Can we fallback to global installed prettier bin instead if prettier not found from package.json ? 1
Read more >Prettier plugin's config "prettier package" should default to ...
Ideally, the field "Prettier package:" would be set to the current project's ./node_modules/prettier if it exists (or, as a fallback, the global one, ......
Read more >How to configure Prettier and VSCode - Gleb Bahmutov
VSCode setup # To use the Prettier we have just installed from VSCode we need to install the Prettier VSCode extension: Launch VS...
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
I propose this order:
local > global > bundled
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.