Swiftpack.co -  cx-org/CXShim as Swift Package
Swiftpack.co is a collection of thousands of indexed Swift packages. Search packages.
A virtual Combine interface that allows you to switch between different Combine implementations.
.package(url: "https://github.com/cx-org/CXShim.git", from: "0.4.0")


Github CI Status Install Supported Platform

CXShim is a virtual Combine interface that allows you to switch berween system Combine and open source Combine.

With CXShim, you shoudn't write different code for different Combine. If you find you are in need of it, please file an issue.


Add the following line to the dependencies in your Package.swift file:

.package(url: "https://github.com/cx-org/CXShim", .upToNextMinor(from: "0.4.0"),


  • Swift 5.0+


Why do I need it?

Because Combine has system limitation, and open source Combine doesn't compatible with SwiftUI. With CXShim, You can easily write one package that compatible with SwiftUI, support Linux, and can backward deploy to iOS 9.0.

Is there any downside?

No, CXShim introduce no extra dependency, no runtime cost, no binary size incrementation. It's not infectious. Migrating from Combine to CXShim is a non-breaking change.

Looks great! How can I adopt it?

If your package use Combine, just replace every import Combine with import CXShim, everything will still works fine. And with a little adjustment, your package can support Linux and lower system as well.

Why this library requires iOS 13+ / macOS 10.15+?

Because system Combine is used by default on Apple platforms. Don't worry, you can choose open source Combine manually and get rid of system requirement.

How do I choose which Combine to use?

You can choose Combine implementation by setting environment variable CX_COMBINE_IMPLEMENTATION.

Combine (default on Apple platforms) Combine
CombineX (default on Linux) CombineX
Others See below

# for CLI tools, execute with env variable
$ swift build ...
$ xcodebuild ...

# for Xcode GUI, reopen Xcode with env variable
$ killall Xcode
$ open Package.swift

How it actually works?

CXShim conditionally re-export appropriate Combine implementation. It also fill the gap between different Combine. For example, you would have needed to write different code for Combine and CombineX:

#if BACKWARD_DEPLOYMENT // we are target on lower system and use CombineX
// This method is under cx namespace because `URLSession.dataTaskPublisher` 
// can't be overloaded and always use system Combine.
let pub = URLSession.shared.cx.dataTaskPublisher(for: url)
#else // use system Combine
let pub = URLSession.shared.dataTaskPublisher(for: url)

With CXShim, you don't need compilation flags anymore:

import CXShim
// `cx` namespace is available even if you're using system Combine
let pub = URLSession.shared.cx.dataTaskPublisher(for: url)

Can I use other open source Combine?

Yes you can! CXShim support every known Combine implementations and will support any future one. Just set environment variable CX_COMBINE_IMPLEMENTATION to their respective value. If your library is not listed below, feel free to open an issue.

OpenCombine OpenCombine

Disclaimer: These project are not part of CombineX. They may have different consistent level with Apple's Combine than we promised, and not necessarily pass our test suit. We do not make any warranty of any kind for them.


Stars: 1
Last commit: 3 weeks ago

Ad: Job Offers

iOS Software Engineer @ Perry Street Software
Perry Street Software is Jack’d and SCRUFF. We are two of the world’s largest gay, bi, trans and queer social dating apps on iOS and Android. Our brands reach more than 20 million members worldwide so members can connect, meet and express themselves on a platform that prioritizes privacy and security. We invest heavily into SwiftUI and using Swift Packages to modularize the codebase.

Release Notes

3 weeks ago

Give CXShim its own repo!

Swiftpack is being maintained by Petr Pavlik | @ptrpavlik | @swiftpackco | API