`@fedify/cli` doesn't work well after `fedify init` depends on different download source

[1673beta]

Summary

After execute fedify init with Fedify 2.0.5, it behaves differently depends on download source. I don't use configuration file that supported after Fedify 2.0.0.

Expected Behavior

Should behaves as documented

Actual Behavior

Behaves differently depends on download source:

• Node.js(npm)
  • The framework selection screens appears first, not the runtime selection, and cannot select bare-bones.
• Homebrew
  • After executed, it stucks after choosing directory.
• Deno
  • Displays the error written in logs and cannot execute any fedify commands.

Environment

OS: macOS Tahoe 26.1
Runtime: Deno, Node.js, Homebrew
Runtime Version:

• Deno 2.7.5
• Node.js v22.15.0 / npm 10.9.2
• Homebrew 5.1.0

Logs / Screenshots

Screenshot of installation and execution via Node.js (npm)

Logs that displayed after run fedify init

$ fedify init
error: Uncaught (in promise) TypeError: The "path" argument must be of type string. Received undefined
export const PACKAGES_PATH = joinPath(
                             ^
    at assertPath (ext:deno_node/path/_util.ts:10:11)
    at join (ext:deno_node/path/_posix.ts:95:5)
    at https://jsr.io/@fedify/init/2.0.5/src/action/const.ts:3:30

Steps to Reproduce

A. install via npm

sudo npm install -g @fedify/cli
fedify init

B. Install via Homebrew

brew install fedify
fedify init

C. Install via deno

deno install \
  -gA \
  --unstable-fs --unstable-kv --unstable-temporal \
  -n fedify \
  jsr:@fedify/cli

[dahlia]

Thanks for reporting; we will investigate and fix it in the next patch release!

[dahlia]

I investigated this and confirmed that #623 is actually grouping together multiple different problems with different root causes, rather than a single bug.

I split out the parts that I could reproduce into separate sub-issues:

• @fedify/init crashes on JSR and Deno because it assumes import.meta.dirname is available #624
• fedify init prompt flow and documented CLI options are out of sync #625

The JSR/Deno failure is a real runtime bug in @fedify/init, while the npm behavior appears to be a separate implementation/documentation mismatch.

I was not able to reproduce the Homebrew/macOS-specific “stuck after choosing directory” behavior in my current environment, so I did not split that part into its own issue yet. That part may still need separate investigation on macOS.

I'll keep this issue as the umbrella tracker for the overall report, and the concrete follow-up work can happen in the sub-issues above.

[1673beta]

About the Homebrew-specific problem, if I execute with pipes (fedify init | tee debug.log) it succeeds, but without any pipes (fedify init), the problem still causes on my environment... I shall continue to investigate whether this constitutes an environment-specific issue unique to my local configuration.