# chore: Extract \`assets\` module out of zed crate\. \(\#3957\) · gitcafe/zed

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

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

Visibility: public

Requested revision: ae6d09b9b25abbdb0877eda35c8c79803bf47d1c

Requested commit: ae6d09b9b25abbdb0877eda35c8c79803bf47d1c

Commit: ae6d09b9b25abbdb0877eda35c8c79803bf47d1c

Tree: 9553a40dae316bf95a0c8f9270ea2cfe84d9640b

Author: Piotr Osiewicz

Committer: GitHub

## Message

```
chore: Extract `assets` module out of zed crate. (#3957)

This essentially shaves off about 10% off of an incremental build after
project change and potentially more if you're changing stuff like
`welcome` that's very close to the `zed` crate in the dep graph. That's
because macro expansion takes place even in incremental builds it seems?
And zed (lib) + zed (bin) could take up to 4 seconds out of an
incremental build, which is a *lot* in a 10s build. In reality though it
shaves 1 second off of 5 seconds incremental 'welcome'/ 1s off of 10s
'project' builds.

Note that we had `assets` crate in the past (removed in #2575 /cc
@maxbrunsfeld), but this is a bit different, because `assets` is a
dependency of *just* zed and nothing else. We essentially cache macro
expansion results ourselves.

Release Notes:

- N/A
```

## Parents

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

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