# Issue 10 - June 6th

**URL:** https://community.tuist.dev/t/issue-10-june-6th/561
**Category:** Swift Stories (Newsletter)
**Created:** [May 16, 2025, 10:27am UTC](https://community.tuist.dev/t/issue-10-june-6th/561 "2025-05-16T10:27:37Z")
**Posts on this page:** 1
**Showing post:** 30

<div class="post-metadata">

### Author: ![marekfort](https://community.tuist.dev/user_avatar/community.tuist.dev/marekfort/32/8_2.png) [@marekfort](https://community.tuist.dev/u/marekfort)
#### Post date: [June 15, 2025, 7:15pm UTC](https://community.tuist.dev/t/issue-10-june-6th/561/30 "2025-06-15T19:15:44Z")

</div>

> [@adarhef](#):
>
> I imagine it’s because it’s treated like a normal dependency and built like all the others.  
> I’m wondering if/when Tuist can start supporting Swift Syntax pre-built binaries?

If you are using the XcodeProj-based integration, then we’d need to add support for this, indeed. Because Tuist enables you to cache external dependencies, you can build a particular version of Swift syntax _once_ and then reuse that across all your projects even without this feature, so we don’t feel there’s such a _strong_ need to add support for this. However, it’d still be a nice addition and we’d be happy to help anyone who’d like to contribute this.

We would most likely need to re-implement a version of the [PrebuiltManager](https://github.com/swiftlang/swift-package-manager/blob/ff7ea75b95e503bd3f22fcf8cf09e274561c3c10/Sources/Workspace/Workspace%2BPrebuilts.swift#L164) from SwiftPM to download the binaries and then replace the source variant with the prebuilt variant in the [PackageInfoMapper](https://github.com/tuist/tuist/blob/b2ab5442b91245690c3f9ab5a16b9bf030a28c28/Sources/TuistLoader/SwiftPackageManager/PackageInfoMapper.swift) (or later on in its own repo).

Feel free to create an issue for this one on GitHub 🙂

---

_[View the full topic](https://community.tuist.dev/t/issue-10-june-6th/561)._