marceloglacial

# GitHub Copilot Instructions for React and Next.js Projects

This file provides guidelines for GitHub Copilot to ensure consistent, clean, and performant code generation for React and Next.js applications.

## General Principles

- **Clean Code:** Prioritize **readability, maintainability, and reusability**.
- **Conciseness:** Aim for concise and expressive code.
- **Descriptive Naming:** Use clear and descriptive names for variables, functions, components, and files (e.g., `getUserProfile`, `ProductCard`, `useAuth`).
- **DRY (Don't Repeat Yourself):** Extract reusable logic into functions, custom hooks, or components.

alexanderbuhler

This gist may be your full solution or just the starting point for making your Tailwind v4 projects backwards compatible.

What it does

• Effectively getting browser support down to Chrome 99 (and basically everything supporting @layer)
• Pre-compute oklab() functions
• Pre-compute color-mix() functions (+ replace CSS vars inside them beforehand)
• Remove advanced instructions (colorspace) from gradients
• Provide support for nested CSS (used by dark mode or custom variants with &)
• Transform translate, scale, rotate properties to their transform: ... notation
• Add whitespace to var fallbacks var(--var,) > var(--var, ) to help older browsers understand

tarunsahnan

// While using [this solution](https://github.com/testing-library/react-testing-library/issues/1209#issuecomment-2400054404), 
// I encountered a timeout issue caused by API calls in my components. Each component was waiting for its 
// API call to complete before rendering, which led to delays and affected the flow to subsequent components. 
// To resolve this, I refactored the logic so that the API calls are initiated in parallel. 
// Then, the function waits for all components to finish rendering.


import { render } from "@testing-library/react";
import React, {
  Children,

manzt

My Minimal TypeScript Monorepo Setup for ESM Libraries

After a deep dive looking up best practices for TypeScript monorepos recently, I couldn't find anything that suited my needs:

1. Publish individual (typed) packages to NPM with minimal config.
2. Supports fast unit testing that spans the entire project (e.g., via Vitest)
3. Ability to have an interactive playground to experiment with the API in a real-time (e.g., via Vite)

Most solutions point to TypeScript project references,

zchee

--- Actions ---
$Copy                                              <M-C>
$Cut                                               <M-X> <S-Del>
$Delete                                            <Del> <BS> <M-BS>
$LRU                                              
$Paste                                             <M-V>
$Redo                                              <M-S-Z> <A-S-BS>
$SearchWeb                                         <A-S-G>
$SelectAll                                         <M-A>
$Undo                                              <M-Z>