# Do not use prettier for formatting node_modules/\*\* files \(\#3286\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/b157453630f5ed99803ff9e5a66113a6f026821a)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: b157453630f5ed99803ff9e5a66113a6f026821a

Requested commit: b157453630f5ed99803ff9e5a66113a6f026821a

Commit: b157453630f5ed99803ff9e5a66113a6f026821a

Tree: 3838192ad4eba5689f3c108f315e13531b133ee8

Author: Kirill Bulatov

Committer: GitHub

## Message

```
Do not use prettier for formatting node_modules/** files (#3286)

Fixes

> the most annoying thing i'm running into right now is that when i'm
patching something inside node_modules, Zed tries to pretty-format it
according to my prettier config. this messes up the patch because it has
formatting changes now. i need the pretty formatting on save to be off
inside node_modules, that never makes sense

feedback from #influencers 

Do note though, that language servers will still format any file inside
node_modules, but at least it's not prettier now.
VSCode seem to format the node_modules/** files via language servers
too, so that seems ok for now, and the rest could be fixed during

> "project diagnostics" (eslint) seem to be running inside node_modules,
e.g. i'm seeing 3182 "errors" in my project. that doesn't make sense and
probably wastes resources in addition to being annoying

feedback later.

Release Notes:

- Fixed prettier formatting files inside node_modules
```

## Parents

- [27b3378020c149f68b744b12ee55115bd2c3f876](https://git.cafe/gitcafe/zed/commit/27b3378020c149f68b744b12ee55115bd2c3f876?format=markdown)

- [f55d89088bcdc43d1ac4f7ac787d6dc732e7c0ea](https://git.cafe/gitcafe/zed/commit/f55d89088bcdc43d1ac4f7ac787d6dc732e7c0ea?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/b157453630f5ed99803ff9e5a66113a6f026821a?format=markdown)