# Use serde 1.0.221 instead of serde_derive hackery \(\#38137\) · gitcafe/zed

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

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

Visibility: public

Requested revision: 37239fd66bfdb104bdd8c4c81c797ed65f6cd13d

Requested commit: 37239fd66bfdb104bdd8c4c81c797ed65f6cd13d

Commit: 37239fd66bfdb104bdd8c4c81c797ed65f6cd13d

Tree: 88782421656ad82769aad4d859ab3467f203190c

Author: Piotr Osiewicz

Committer: GitHub

## Message

```
Use serde 1.0.221 instead of serde_derive hackery (#38137)

serde 1.0.221 introduced serde_core into the build graph, which should
render explicitly depending on serde_derive for faster build times an
obsolote method.

Besides, I'm not even sure if that worked for us. My hunch is that at
least one of our deps would have `serde` with derive feature enabled..
and then, most of the crates using `serde_derive` explicitly were also
depending on gpui, which depended on `serde`.. thus, we wouldn't have
gained anything from explicit dep on `serde_derive`

Release Notes:

- N/A
```

## Parents

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

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