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.

In today’s development landscape, parsing is often associated primarily with handling JSON from server API calls.

Mobile and frontend developers know how important UI design is for the success of their apps.

In a previous post, we covered how to build a tool that runs system commands, by taking advantage of the Command package instead of using the Process API.

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.

CLI tools often need to run other commands behind the scenes.

Deployment of server side Swift applications is one of the biggest challenges many developers face.

In a previous post, we detailed some of the approaches one can use when building Swift binaries, for different operating systems and architectures.

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.

You finished the first version of your new shiny Swift tool, and now you want to make it available to your colleagues, or maybe share it with the world.

One of the greatest advantages of using Swift for building tools, is the familiarity you might already have with it.

When building a command line tool using Swift, there are a few different approaches you can choose.

If you’re a developer that programs in Swift, changes are extremely high that you are familiar with Xcode.

Welcome to the third and final part of this series, the interactive guide to the Swift Argument Parser.

After the first post explaining the basics of the Swift Argument Parser, the second part is here!

About to build your next command line tool?

When developing a Lambda or Vercel function using Swift, you might in a first place try to use the print() function to write logs.

If you ever got confused when editing a Package.swift file, and didn’t get much help from Xcode your IDE’s code completion, you arrived at the right place!

Hello there.