In November, I released Inferno: an open-source collection of Metal shaders for SwiftUI developers, making it easy to create gorgeous special effects in your iOS apps. https://github.com/twostraws/Inferno
GitHub - twostraws/Inferno: Metal shaders for SwiftUI.

Metal shaders for SwiftUI. Contribute to twostraws/Inferno development by creating an account on GitHub.

GitHub
Two months later, I released Vortex: a high-performance particle effect system for SwiftUI, so you can bring effects such as confetti, fireworks, fire, and more into your apps. https://github.com/twostraws/Vortex
GitHub - twostraws/Vortex: High-performance particle effects for SwiftUI.

High-performance particle effects for SwiftUI. Contribute to twostraws/Vortex development by creating an account on GitHub.

GitHub
Today, another two months later, I just released my third and final open-source project, at least for now. It's called Ignite, and it's a Swift static website generator. Your entire site is written as Swift code, then compiled to HTML, JavaScript, and CSS. https://github.com/twostraws/Ignite
GitHub - twostraws/Ignite: A static site generator for Swift developers.

A static site generator for Swift developers. Contribute to twostraws/Ignite development by creating an account on GitHub.

GitHub
@twostraws When I add the package in Xcode, I get the error Failed to resolve package dependencies. This is a brand new Xcode project.
@tapforms @twostraws Is this with Xcode 15.3? I had similar issues and went back to 15.2. Happier now.
@titociuro @twostraws Yes 15.3. The package that shows in the project navigator also has nothing in it when I allow Xcode to add it anyway.
@tapforms @twostraws Yup. Seen it. My SPM issues have been reduced dramatically (actually, not an issue anymore) with 15.2.
@titociuro @twostraws but I wonder if maybe the package file needs something setup differently for Xcode 15.3?
@tapforms @twostraws Perhaps? But here’s the thing… I have seen issues with Vapor and other packages as well. Even the packages disappear from what a few seconds earlier was all fine. And then a barrage of errors. My limited interaction proved frustrating with 15.3 so I went back. I wasted way too much time chasing I-don’t-know-what. And the message wasn’t helpful at all, so I bailed.
@titociuro @twostraws Interesting. I have many other SPM packages in my Xcode 15.3 project without any issues. Something with this package won't work though. I don't really want to go back to Xcode 15.2 though. Hopefully Paul can think of a solution for this package. I'd like to write a database export function using Ignite to build a website from a database.