Enhance CLI Init Process for Compatibility and Convenience

[tyeetale]

Description:

So I recently started using this repo for my Expo project, and I noticed a couple of hiccups as a first-time user.

Issue Overview

Currently, the CLI initialization process lacks two critical functionalities, which hinder its usability and compatibility. This issue aims to address these gaps to enhance user experience and ensure seamless integration with the latest dependencies.

Proposed Changes

1. Ensure NativeWind v4

The CLI should enforce the download of NativeWind v4 instead of something like nativewind: ^2.0.11, given that only v4 will support more recent versions of Tailwind CSS past [email protected]. This step is essential to maintain compatibility and enable users to leverage the latest features and improvements offered by Tailwind CSS.

2. Download Utils File if Nonexistent

Additionally, the CLI doesn't seem to install the lib/utils.ts file automatically. While the CLI does check for the existence of the utils file during initialization, it's not downloading it if it doesn't exist. This breaks the flow when I go to add components and the utils file is missing.

Expected Outcome

By implementing these enhancements, users will benefit from a more robust and user-friendly CLI initialization process. This will streamline the setup process, ensure compatibility with the latest dependencies, and minimize manual interventions, thereby enhancing overall usability and efficiency.

[tyeetale]

Thinking about it further, the best option for the utils file would be to directly copy the setup from shadcn/ui and set the location in a components.json file, as it's frustrating to have to relabel imports with new components if a user chooses not to have lib/utils.ts.