swiftlang/swift-package-manager

`swift package init --package-path <dir-does-not-exists>` does not create the directory

Open

#8393 opened on Mar 20, 2025

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Swift (10,145 stars) (1,462 forks)batch import
buggood first issueswift package

Description

Is it reproducible with SwiftPM command-line tools: swift build, swift test, swift package etc?

  • Confirmed reproduction steps with SwiftPM CLI. The description text must include reproduction steps with either of command-line SwiftPM commands, swift build, swift test, swift package etc.

Description

When trying to create a new package, using the --package-path option fails if the directory does not exist.

Expected behavior

swift package init --package-path <dir> should:

  • create the directory, and populate the package if it does not exists
  • should populate the package if the directory exists and is empty
  • prompt the user for action if the directory exists and is non-empty
  • should error if <dir> exists as a file

Actual behavior

directory does not exists

❯ swift package init --package-path Foo
error: chdir error: No such file or directory (2): /Users/bkhouri/Downloads/Foo

Directory exists and is empty

❯ swift package init --package-path Foo
Creating library package: Foo
Creating Package.swift
Creating .gitignore
Creating Sources
Creating Sources/Foo/Foo.swift
Creating Tests/
Creating Tests/FooTests/
Creating Tests/FooTests/FooTests.swift

Directory Exists and contains a Package.swift

❯ swift package init --package-path Foo
Creating library package: Foo
error: a manifest file already exists in this directory

Directory exists and is not empty (does not contains Package.swift)

❯ swift package init --package-path Foo
<...SNIP...>
❯ rm -rf Foo/Package.swift
❯ swift package init --package-path Foo
Creating library package: Foo
Creating Package.swift

Steps to reproduce

swift package init --package-path ./does-not-exists-yadda-yadda

Swift Package Manager version/commit hash

Swift Package Manager - Swift 6.2.0-dev

Swift & OS version (output of swift --version ; uname -a)

❯ swift --version Apple Swift version 6.2-dev (LLVM 162ee50b401fff2, Swift 57288d13c9f3c02) Target: arm64-apple-macosx15.0 Build config: +assertions

❯ uname -a Darwin BKs-Work-M1Pro-MacBook-Pro-2.local 24.4.0 Darwin Kernel Version 24.4.0: Tue Mar 11 22:26:20 PDT 2025; root:xnu_development-11417.101.12~4/DEVELOPMENT_ARM64_T6000 arm64

Contributor guide

Tech stack
swift
Domain
cli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Swift basicsSwiftPM codebase familiarity
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Start by examining the Swift package manager source code in the `swift package manager` repository. Focus on the command implementation for `swift package init`, likely in `Sources/Commands/SwiftPackageInit.swift`. The current behavior errors when the directory does not exist. The fix should add logic to create the directory if it does not exist, following the expected behavior outlined in the issue. Also check for existing tests for ` package path` in `Tests/CommandsTests/` to understand testing patterns.