Fix(shadcn init): improve shadcn package behavior

[Anas-github-acc]

PR: Fix Project Directory Creation Issues ( shadcn init )

Issue

Changes

• Ensured cwd resolution before override: in shadcn/commands/init.ts Placed the options ...opts before the cwd resolution logic to prevent any overrides that cause incorrect working directory resolution.
  

Issue

The issue is that if a folder exists with the same path when you try to init a new next.js project using shadcn init and the folder contain some files (e.g., my-app contains content2.txt) but lack package.json file, the program continues to execute and encounters the error during next.js create-next-app. The unclear error message makes it hard for user to identify error and additional time to get to the error message is frustrating.

How i fixed it

• Attempt to create the project directory (used fs.mkdirSync)
  • If it already exists, check if it is empty (reading first entry of the directory).
  • If not empty, show a clear error and exit.
  • If not writable or path does not exist, show a clear error and exit.
  • if exists but is empty, proceed with project creation.

Impact

1. Proper writable permission check for the target directory.
2. This prevents cryptic errors when the target folder is not suitable.

Test

• Some tests in shadcn/utils/create-project.test.ts have been added, and others have been updated

[vercel]

@Anas-github-acc is attempting to deploy a commit to the shadcn-pro Team on Vercel.

A member of the Team first needs to authorize it.