fastjs-team/core

bug(cli): can't create with only using npm

Closed this issue · 1 comments

xiaodong2008 commented

What is the current behavior?

Documents/Program/fastjs-team via  v20.12.1
❯ npm create fastjs
sh: create-fastjs: command not found
npm ERR! code 127
npm ERR! path /Users/xiaodong/Documents/Program/fastjs-team
npm ERR! command failed
npm ERR! command sh -c create-fastjs

npm ERR! A complete log of this run can be found in: /Users/xiaodong/.npm/_logs/2024-04-29T00_28_44_259Z-debug-0.log

What is the expected behavior?

Documents/Program/fastjs-team via  v20.12.1
❯ pnpm create fastjs
.../Library/pnpm/store/v3/tmp/dlx-48275 | +62 ++++++
.../Library/pnpm/store/v3/tmp/dlx-48275 | Progress: resolved 84, reused 62, downloaded 0, added 62, done

🛠️ Fastjs Cli 1.0.0-beta.3
Author: @xiaodong2008

Finding available package managers:
✔ Detected package manager pnpm
✔ Detected package manager yarn
✖ Package manager bun not found
✔ Detected package manager npm
Found 3 package managers in 599ms

? Enter the name of the app: (fastjs-app)

Steps to reproduce the problem

When using npm init or npm create, yarn or pnpm doesn't have this problem.

Link to minimal reproduction

No response

System Info

System:
    OS: macOS 14.4
    CPU: (8) arm64 Apple M2
    Memory: 256.59 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
Binaries:
    Node: 20.12.1 - ~/Library/Caches/fnm_multishells/35933_1714347794853/bin/node
    Yarn: 1.22.22 - ~/Library/Caches/fnm_multishells/35933_1714347794853/bin/yarn
    npm: 10.5.0 - ~/Library/Caches/fnm_multishells/35933_1714347794853/bin/npm
    pnpm: 8.15.6 - ~/Library/Caches/fnm_multishells/35933_1714347794853/bin/pnpm
Browsers:
    Chrome: 124.0.6367.91
    Safari: 17.4

Any additional comments?

No response

Confirmations

  • I'm using/tried the latest version of fastjs and the bug is still there
  • I have read the Code of Conduct
  • I have read the Issue Reporting Guidelines
  • I have searched for similar issues in both open and closed tickets and cannot find a duplicate
  • I know that any inappropriate content may cause the maintainer to take action base on the Code of Conduct
xiaodong2008 commented

Fixed in v1.0.0-beta.5