Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

how to create new project?

Open
#390 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
cli

Research direction

Reproduce the failure using the documented cocos create --project ./my-game flow, then run the generated cocos create --project . command from the issue. Start at the cocos create CLI entry point and trace how an existing target path is handled. Done means the intended project-creation flow succeeds or the failure is clearly explained and covered by the relevant test.

Written by the indexing model from the issue text.

Description

I try to build and create new project but have this error:
antn@antns-Mac-mini cocos % cocos create --project ./my-game
Creating project...
Path: /Users/antn/Documents/cocos/my-game
Type: 3d
✓ Project created successfully!
Next steps:
cd /Users/antn/Documents/cocos/my-game
cocos create --project .
antn@antns-Mac-mini cocos % cd /Users/antn/Documents/cocos/my-game
antn@antns-Mac-mini my-game % cocos create --project .
Creating project...
Path: /Users/antn/Documents/cocos/my-game
Type: 3d
Warning: target path already exists, will try to create inside it.
✗ Failed to create project.

Dominant language
TypeScript
Stars
450
Forks
158
Avg merge
3d 4h
Merged PRs (30d)
33

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cocos/cocos-cli

All issues in cocos/cocos-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.