An open API service indexing awesome lists of open source software.

https://github.com/zigzagdev/portfolio-frontend


https://github.com/zigzagdev/portfolio-frontend

Last synced: 4 months ago
JSON representation

Awesome Lists containing this project

README

          

# React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

- [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/README.md) uses [Babel](https://babeljs.io/) for Fast Refresh
- [@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react-swc) uses [SWC](https://swc.rs/) for Fast Refresh

## Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules:

```js
export default tseslint.config({
extends: [
// Remove ...tseslint.configs.recommended and replace with this
...tseslint.configs.recommendedTypeChecked,
// Alternatively, use this for stricter rules
...tseslint.configs.strictTypeChecked,
// Optionally, add this for stylistic rules
...tseslint.configs.stylisticTypeChecked,
],
languageOptions: {
// other options...
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
},
})
```

You can also install [eslint-plugin-react-x](https://github.com/Rel1cx/eslint-react/tree/main/packages/plugins/eslint-plugin-react-x) and [eslint-plugin-react-dom](https://github.com/Rel1cx/eslint-react/tree/main/packages/plugins/eslint-plugin-react-dom) for React-specific lint rules:

```js
// eslint.config.js
import reactX from 'eslint-plugin-react-x'
import reactDom from 'eslint-plugin-react-dom'

export default tseslint.config({
plugins: {
// Add the react-x and react-dom plugins
'react-x': reactX,
'react-dom': reactDom,
},
rules: {
// other rules...
// Enable its recommended typescript rules
...reactX.configs['recommended-typescript'].rules,
...reactDom.configs.recommended.rules,
},
})
```
---

## Tailwind CSS version lock (v3.3.5 fixed)

> ⚠️ **Important:** This project uses **Tailwind CSS v3.3.5**.
Do not upgrade to Tailwind v4. Doing so will cause PostCSS plugin errors and break the build.

### Why?

Tailwind v4 separates its PostCSS plugin into `@tailwindcss/postcss`, which is **incompatible** with the current `postcss.config.js`.

If you see the following error:

```
[plugin:vite:css] [postcss] It looks like you're trying to use tailwindcss directly as a PostCSS plugin...
```

you’re accidentally using v4.

### How to fix:

1. Uninstall all Tailwind packages:

```bash
npm uninstall tailwindcss @tailwindcss/postcss @tailwindcss/node
```

2. Reinstall Tailwind v3.3.5:

```bash
npm install tailwindcss@3.3.5
```

3. Set your postcss.config.js to use the Tailwind plugin:

```js
module.exports = {
plugins: {
tailwindcss: {},
autoprefixer: {},
},
};
```