SwiftToolkit.dev

Dev Conversations is a monthly series where Swift Toolkit features members of Swift work groups, content creators, and people who contribute to the Swift community, focused on tooling, developer experience and Server Side Swift.

Every once in a while you face a new paradigm that changes everything you knew about a specific domain.

Dev Conversations is a monthly series where Swift Toolkit features members of Swift work groups, content creators, and people who contribute to the Swift community, focused on tooling, developer experience and Server Side Swift.

Server-side applications, especially ones that run on multiple servers, often need to share data temporarily.

Dev Conversations is a monthly series where Swift Toolkit features members of Swift work groups, content creators, and people who contribute to the Swift community, focused on tooling, developer experience and Server Side Swift.

The first part of this series covered generating completion scripts for Swift binaries built with the argument parser.

Dev Conversations is a monthly series where Swift Toolkit features members of Swift work groups, content creators, and people who contribute to the Swift community, focused on tooling, developer experience and Server Side Swift.

Previously, we’ve covered in our Argument Parser Guide and other posts the basics of the Swift Argument Parser, showing you how to build tools with it and use all the customizations it offers: commands, subcommands, arguments, options, and flags.

In August 2025, the Swift Server Work Group announced the V2 beta release of the Swift implementation of the AWS Lambda Runtime.

Dev Conversations is a monthly series where Swift Toolkit features members of Swift work groups, content creators, and people who contribute to the Swift community, focused on tooling, developer experience and Server Side Swift.

Reacting to file changes is a common technique in many applications.

It’s time for another post in the Let’s Build series!

Over the upcoming Let’s Build posts, we’ll be building fun CLI applications.

Dev Conversations is a monthly series where Swift Toolkit features members of Swift work groups, content creators, and people who contribute to the Swift community, focused on tooling, developer experience and Server Side Swift.

Last week, as part of WWDC 2025, Apple announced two new open source projects, with almost identical names.

In the 8th Dev Conversations episode, with Pedro and Marek, one of the discussed topics was their work on multiple features from Tuist, that when extracted to public Swift packages, can also be extremely useful to the community .

In a previous post, Distribute Your Swift CLIs for macOS, Pedro Piñera explained how to build Swift executables for macOS and distribute them as pre-compiled binaries.

Dev Conversations is a monthly series where Swift Toolkit features members of Swift work groups, content creators, and people who contribute to the Swift community, focused on tooling, developer experience and Server Side Swift.

A very common scenario when using CLI tools is to chain commands together.

While developing a CLI tool, it is a common practice to print values to the console.

When developing AWS Lambda functions, there are multiple ways to trigger it once you deploy it.

Dev Conversations is a monthly series where Swift Toolkit features members of Swift work groups, content creators, and people who contribute to the Swift community, focused on tooling, developer experience and Server Side Swift.

In the first part of this series, we covered the basics of Sake, a CLI tool that lets you write and run tasks in Swift for your projects, instead of shell scripts.

If you’ve worked with developer tools, chances are high that you heard about the make utility.

When shipping iOS or macOS applications, the process of distributing them is relatively simple, and familiar to most developers, thanks to Xcode and the AppStore.

Dev Conversations is a monthly series where Swift Toolkit features members of Swift work groups, content creators, and people who contribute to the Swift community, focused on tooling, developer experience and Server Side Swift.

For developers who are used to iOS development, the process of deploying a Server Side Swift app can be a bit intimidating, as Xcode brings everything you need: the compiler, the SDK, the debugger, and the simulator.

Here in SwiftToolkit.dev we’ve already repeated this motto: better than having great tools, is making them run automatically, in the right time.

The Raspberry Pi is a series of single-board computers that became very popular in the last few years.

Dev Conversations is a monthly series where Swift Toolkit features members of Swift work groups, content creators, and people who contribute to the Swift community, focused on tooling, developer experience and Server Side Swift.

In the previous post, we built a basic version of the tree program: a command line tool that prints a visual representation of a directory tree, given a path to a directory.

Today SwiftToolkit is starting a new series: Let’s Build.

When compared to regular applications, command line tools have a limited graphic interface: the terminal.

Dev Conversations is a monthly series where Swift Toolkit features members of Swift work groups, content creators, and people who contribute to the Swift community, focused on tooling, developer experience and Server Side Swift.

In a previous post, we explained how to use Mustache templates in Swift for code generation and any templating task.

If you’ve read previous posts and series, you already know how this website likes the Swift Argument Parser.

In the last Dev Conversations episode with Mikaela Caron, she shared how hard it was for her to deal with file uploads in a Vapor App.

2024 is almost over.

Dev Conversations is a monthly series where Swift Toolkit features members of Swift work groups, content creators, and people who contribute to the Swift community, focused on tooling, developer experience and Server Side Swift.

When writing your own tools, generating code is a very frequent need.

In one of our earlier articles, we made an introduction to SwiftCloud, a package that lets you define your cloud infrastructure using Swift code.

In the Dev Conversations episode with Adam Fowler and Joannis Orlandos, where we discussed Hummingbird and Docker, a reader submitted the following comment: How would I make the Mac the Cloud Host provider in this situation?

Dev Conversations is a monthly series where Swift Toolkit features members of Swift work groups, content creators, and people who contribute to the Swift community, focused on tooling, developer experience and Server Side Swift.

In the previous posts of this series, we covered how to setup a VS Code Dev Container for a Hummingbird app, and also how to use Docker Compose to use PostgreSQL database in that same app.

The first post of this series explored how to take advantage of Dev Containers, a useful VS Code feature that enables to run and debug Swift command line or server apps in a Linux container.

In the last episode of Dev Conversations, Adam Fowler and Joannis Orlandos emphasized how useful Dev Containers are when developing server apps in Swift with VS Code.

Dev Conversations is a monthly series where Swift Toolkit features members of Swift work groups, content creators, and people who contribute to the Swift community, focused on tooling, developer experience and Server Side Swift.

The standard way to use the Swift Argument Parser consists of basically two steps: creating the commands conforming to ParsableCommand (or its async version), followed by implementing the run() method.

You might have heard the concept of Copy On Write before, and asked yourself what it means.

Previous posts covered how important a great developer experience is when creating CLI tools.