chore: add eslint-plugin-sort and eslint-plugin-prettier

[Dargon789]

f1dd440
49c4050
484b187

[sourcery-ai]

Sorry @Dargon789, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly overhauls the project's internal architecture and user experience. It streamlines template management by replacing an external dependency with a custom solution, enabling more robust and flexible template creation, including support for local templates. The post-installation init script has been upgraded with critical version checks and improved renaming capabilities, alongside a new optional setup task for automated project configuration. Furthermore, the developer workflow is enhanced through new CLI options, integration of ESLint sorting and Prettier for code consistency, and a migration to lefthook for managing Git hooks.

Highlights

• Refactored Template Handling: The external @beeman/repokit dependency has been replaced with internal utility modules (fetch-templates.ts, menu-utils.ts, template-schema.ts), providing greater control and reducing external dependencies for template fetching and menu generation.
• Introduced Local Template Support: The application now supports creating new projects from local file paths (e.g., local:/path/to/template), offering enhanced flexibility for development and custom template usage.
• Enhanced Init Script Execution: The post-template-creation init script has been significantly improved, now including version checks for Anchor and Solana, and refined project renaming logic to correctly handle hyphenated names and prevent path duplication.
• Added Optional Setup Task: A new task has been implemented to automatically run an optional setup script (if defined in package.json) after template installation, which is particularly useful for automating post-installation tasks like building Anchor programs.
• New CLI Options: Two new command-line interface options have been added: --list-template-ids to output available template IDs as a JSON array, and --minimal to quickly select the predefined nextjs-anchor template.
• Integrated ESLint Sorting and Prettier: The ESLint configuration (eslint.config.mjs) now includes eslint-plugin-sort and eslint-plugin-prettier to enforce consistent code style, property sorting, and automatic code formatting.
• Migrated Git Hooks to Lefthook: The project's Git hooks have been migrated from Husky to lefthook, centralizing and streamlining the automation of pre-commit tasks such as linting and JSON formatting.

Ignored Files

• Ignored by pattern: .github/workflows/** (3)
  • .github/workflows/actions/install-dependencies/action.yml
  • .github/workflows/e2e-test.yml
  • .github/workflows/publish-pkg-pr-new.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request significantly refactors the template handling and project setup process, moving away from the external @beeman/repokit dependency to local utility modules for template schema, fetching, and menu logic. Key changes include introducing a new lefthook.yml for pre-commit hooks (replacing previous husky scripts) to manage linting and formatting, and updating the ESLint configuration with new sorting rules. The create-solana-dapp CLI now supports local template paths, a --minimal flag for quick setup, and a --list-template-ids option. The project setup flow has been enhanced with a new task to run an optional setup script (e.g., for Anchor program builds) and improved init script execution, which now includes version checks for Anchor and Solana, and more robust template renaming logic to prevent path duplication. Minor stylistic changes, such as reordering object properties and adding blank lines for readability, were also applied across various files, likely due to the new ESLint sorting rules.

[gemini-code-assist]

The title property has been moved from its original position. This is a stylistic reordering, likely due to the newly introduced sort/type-properties ESLint rule. For consistency, please ensure all properties within an object adhere to the defined sorting order.

    task: async (result) => {

[gemini-code-assist]

The order of properties in the SelectOptions type definition has been reordered. This is a stylistic change, likely due to the newly introduced sort/type-properties ESLint rule. Please ensure consistent property ordering.

): SelectOptions<{ hint?: string | undefined; label: string; value: Template }[], Template> {

[gemini-code-assist]

A blank line has been added before the checkGitVersion function. This is a stylistic change that improves readability by separating function definitions.

function checkGitVersion(): string | undefined {

[gemini-code-assist]

A blank line has been added before the checkGitUserEmail function. This is a stylistic change that improves readability by separating function definitions.

function checkGitUserEmail(): string | undefined {

[gemini-code-assist]

A blank line has been added before the namesValues function. This is a stylistic change that improves readability by separating function definitions.

export function namesValues(name: string): string[] {

[gemini-code-assist]

A blank line has been added before the pmVersionCache constant. This is a stylistic change that improves readability by separating declarations.

Suggested change

	const pmVersionCache = new Map<PackageManager, string>()

[gemini-code-assist]

The order of properties in the baseArgs object has been reordered. This is a stylistic change, likely due to the newly introduced sort/type-properties ESLint rule. Please ensure consistent property ordering in test data.

Suggested change

	instructions: [],
	name: 'test-project',
	targetDirectory: '/template',
	packageManager: 'npm',
	skipGit: false,
	skipInit: false,
	skipInstall: false,
	template: { name: 'basic', description: 'description', repository: '/template' },
	verbose: false,
	target: 'test-project',
	instructions: [],
	targetDirectory: '/template',
	template: { description: 'description', name: 'basic', repository: '/template' },
	verbose: false,
	dryRun: false,
	instructions: [],
	name: 'test-project',
	packageManager: 'npm',
	skipGit: false,
	skipInit: false,
	skipInstall: false,
	target: 'test-project',
	targetDirectory: '/template',
	template: { description: 'description', name: 'basic', repository: '/template' },

[gemini-code-assist]

The order of properties in the baseArgs object has been reordered. This is a stylistic change, likely due to the newly introduced sort/type-properties ESLint rule. Please ensure consistent property ordering in test data.

Suggested change

	packageManager: 'npm',
	skipGit: false,
	skipInit: false,
	skipInstall: false,
	template: { name: 'basic', description: 'description', repository: '/template' },
	targetDirectory: '/template',
	template: { description: 'description', name: 'basic', repository: '/template' },
	name: 'test-project',
	packageManager: 'npm',
	skipGit: false,
	skipInit: false,
	skipInstall: false,
	targetDirectory: '/template',