cli init command erroring when using npm as package manager

[Julian-AT]

Describe the bug
cli innit command fails with npm as package manager.

next-forge version
v2.21.11 (current @latest)

To Reproduce
npx next-forge@latest init [app-name] --package-mananger npm

Expected behavior
Initialize a new next-forge project with npm instead of pnpm

Screenshots

C:\PATH>npx next-forge@latest init example --package-manager npm
Creating new next-forge project...
Failed to initialize project: ENOENT: no such file or directory, chdir 'C:\PATH' -> 'C:\PATH\example'

If manually creating the example dir before running the command:

C:\PATH>npx next-forge@latest init example --package-manager npm
Creating new next-forge project...
Deleting internal content...
Removing pnpm lockfile and workspace config...
Installing dependencies...
Failed to initialize project: Command failed: npm install

Desktop (please complete the following information):

• OS: Win 11

[haydenbleasel]

Found the issue! Was running npm create next-app instead of npx create next-app. Also fixed for bun 👍

[github-actions]

🚀 Issue was released in v3.0.6 🚀