Incorrect Package Manager Detection in npm create pylon@latest

[schettn]

Description:

The current implementation of the package manager (pm) detection in the npm create pylon@latest command always favors yarn due to its reliance on the presence of lock files. This is problematic because the Pylon create command does not include lock files.

Current Behavior:

1. If any of the following lock files are found in the current working directory, it resolves the associated package manager and skips further checks:
   • yarn.lock -> resolves yarn
   • package-lock.json -> resolves npm
   • pnpm-lock.yaml -> resolves pnpm
   • bun.lockb -> resolves bun
2. If no lock files are found, it checks if the yarn, pnpm, or bun commands are available in the environment. If so, it resolves the respective package manager; otherwise, it defaults to npm.

Expected Behavior:

The package manager detection should:

1. Check if the current environment uses a specific package manager (e.g., check for the presence of relevant commands or configurations).
2. If no specific environment configuration is found, fall back to lock file detection and ensure that the detected package manager is available.
3. Accept a preferredPm configuration option. This allows prioritizing a preferred package manager if it's available, such as favoring bun when using the bun runtime. This feature is also required for supporting Deno (Provide a starter for Deno/Hono #41).

Steps to Reproduce:

1. Run npm create pylon@latest in a directory without any lock files.
2. Observe that yarn is favored if it is available, even if another package manager should be preferred based on the environment or configuration.

Proposed Solution:

• Modify the pm detection logic to first check the current environment for a specific package manager.
• If no specific environment configuration is found, proceed with lock file detection.
• Implement the preferredPm configuration to allow users to specify their preferred package manager. This option should be checked first before falling back to environment or lock file detection.
• Ensure compatibility with supporting runtimes like Deno (Provide a starter for Deno/Hono #41).

Additional Context:

• This issue affects the usability of the npm create pylon@latest command, especially in environments where multiple package managers are present.
• Resolving this issue will enhance the flexibility and accuracy of the package manager detection mechanism.

[github-actions]

🎉 This issue has been resolved in version create-pylon-v1.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version @getcronit/pylon-v2.5.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀