Skip to content

feat: configure eslint, prettier, and husky for code formatting#2

Open
kawanofer wants to merge 1 commit intoisabellaherman:mainfrom
kawanofer:fix/config-eslint-prettier-husky
Open

feat: configure eslint, prettier, and husky for code formatting#2
kawanofer wants to merge 1 commit intoisabellaherman:mainfrom
kawanofer:fix/config-eslint-prettier-husky

Conversation

@kawanofer
Copy link
Copy Markdown

feat: configure eslint, prettier, and husky for code formatting

  • Add ESLint config with Next.js, TypeScript, and Prettier integration
  • Configure Prettier with Tailwind CSS and import sorting plugins
  • Set up Husky pre-commit hooks for automated formatting
  • Add VS Code settings for consistent development environment
  • Update package.json with formatting and linting scripts
  • Format all existing TypeScript/JSX files with new rules
  • Add .editorconfig for consistent editor formatting
  • Configure import ordering and code style standards

This ensures consistent code formatting across the project and
automatically formats code on commit via pre-commit hooks.

@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Nov 6, 2025

@kawanofer is attempting to deploy a commit to the isabellaherman's projects Team on Vercel.

A member of the Team first needs to authorize it.

@isabellaherman
Copy link
Copy Markdown
Owner

There are conflicts within the sponsor bar, why are we touching this component? @kawanofer

@kawanofer
Copy link
Copy Markdown
Author

There are conflicts within the sponsor bar, why are we touching this component? @kawanofer

@isabellaherman lint and prettier change all files to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants