Skip to content

gabrielogregorio/valorant-tips

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

467 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Valorant tips

Next JS Vercel TypeScript TailwindCSS Testing-Library cypress Storybook

Codacy Badge Codacy Badge

Introduction this project

This project was developed using NextJs, Typescript and api is available at vavatips-backend.

Access Valorant tips or storybook

Badges

GitHub stars GitHub last commit GitHub contributors GitHub language count GitHub repo size statements branchs functions lines Codacy Badge

Run Project for development

  1. Fully start the backend, available in the vavatips backend repository.
  2. With the backend working, create an .env file, based on the .env.example file.

Contributing with project

Read Contributing.md

Available scripts

Run

# Install full dependencies
yarn

# Ignore storybook dependencies, but resolve in lockfile.
yarn install --ignore-optional
# Run in develop mode
# Open in http://localhost:3000
yarn dev

## Run in production mode
yarn build
yarn start

# Run storybook in localhost:6006
yarn run storybook

Tests

# Tests with react testing library and cypress(e2e)
yarn test
yarn cypress

# Tests in watch mode and coverage
yarn test:watch-all
yarn test:watch-all:coverage

Deploy

# Deploy storybook to github pages
yarn run deploy-storybook-gh-pages

Generics

# Check typescript, eslint, unit tests, integration tests, update badges, e2e tests and audit production
yarn dev
yarn check-all

# Prettier fix all
yarn prettier --write .

# Audit dependencies
yarn audit --groups "dependencies"

# Check libs not used
npx depcheck

# Uprade packages
yarn upgrade-interactive --latest

Vscode extensions for this project

Extension Description Author
Eslint For linting code Microsoft
Prettier - Code formatter For beautifully formate code Prettier
Prettier Eslint Integration prettier and eslint Rebecca Vest
Stylelint For lint in styles Stylelint
Gitignore For use .gitignore CodeZombie
EditorConfig for VS code For basics formatter in code EditorConfig
Tailwind CSS IntelliSense For highlight and autocomplete tailwind Tailwind Labs
TODO Highlight v2 For highlight FIXME: and TODO: Jonathan Clark

pnpm exec playwright test Runs the end-to-end tests.

pnpm exec playwright test --ui Starts the interactive UI mode.

pnpm exec playwright test --project=chromium Runs the tests only on Desktop Chrome.

pnpm exec playwright test example Runs the tests in a specific file.

pnpm exec playwright test --debug Runs the tests in debug mode.

pnpm exec playwright codegen Auto generate tests with Codegen.

We suggest that you begin by typing:

pnpm exec playwright test

pnpm exec playwright test

pnpm exec playwright show-report


This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.

Commits e Hooks de Git

Este projeto utiliza Husky e Commitlint para garantir que todas as mensagens de commit sigam o padrão de Commits Semânticos (Conventional Commits).

Commits Semânticos

As mensagens de commit devem seguir o formato: <tipo>(escopo opcional): <descrição>

Tipos comuns:

  • feat: Nova funcionalidade
  • fix: Correção de bug
  • docs: Alterações na documentação
  • style: Alterações que não afetam o significado do código (espaço em branco, formatação, etc)
  • refactor: Alteração de código que não corrige um bug nem adiciona uma funcionalidade
  • test: Adição de testes ou correção de testes existentes
  • chore: Alterações no processo de build ou ferramentas auxiliares

Exemplo: feat(login): adicionar validação de senha

Hooks de Git

Os hooks são executados automaticamente:

  • pre-commit: Roda o linting (pnpm lint) antes de cada commit.
  • commit-msg: Valida se a mensagem do commit segue o padrão semântico.

Se você precisar rodar manualmente para testar:

  • Linting: pnpm lint
  • Commitlint (último commit): pnpm commitlint --from HEAD~1 --to HEAD --verbose