update main to dev

[ignaciosantise]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 935839a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Copilot]

Pull Request Overview

This PR introduces a new CLI package for the Reown AppKit React Native toolkit. The CLI provides an easy way for developers to scaffold new React Native projects using the AppKit template.

• Adds a new @reown/appkit-react-native-cli package with initialization functionality
• Creates a command-line interface that uses Expo's create-expo tool with a predefined template
• Includes proper TypeScript configuration and build setup for the CLI package

Reviewed Changes

Copilot reviewed 8 out of 9 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
packages/cli/package.json	Package configuration for the new CLI with dependencies and build scripts
packages/cli/src/index.ts	Main CLI entry point that spawns expo create with template URL
packages/cli/src/utils.ts	ASCII art banner for the CLI
packages/cli/tsconfig.json	TypeScript configuration extending root config
packages/cli/bob.config.js	Build configuration for CommonJS, ES modules, and TypeScript outputs
packages/cli/CHANGELOG.md	Changelog documenting the initial CLI feature
packages/cli/.npmignore	NPM ignore file excluding source files from published package
package.json	Root package.json updated to include the new CLI package in workspaces

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Using 'any' type defeats the purpose of TypeScript's type safety. Consider using 'unknown' type instead and properly type guard the error, or create a specific error type.

Suggested change

	console.error('Failed to run Expo initializer:', error?.message || error);
	} catch (error: unknown) {
	// eslint-disable-next-line no-console
	let errorMessage: string;
	if (typeof error === 'object' && error !== null && 'message' in error && typeof (error as any).message === 'string') {
	errorMessage = (error as { message: string }).message;
	} else {
	errorMessage = String(error);
	}
	console.error('Failed to run Expo initializer:', errorMessage);

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud