Troubleshooting

Common issues & fixes.

This page covers common issues you may encounter when setting up or running Cute-Panel locally, along with their solutions.

Environment Variables Not Loaded Correctly

Symptoms:

• Features that rely on API keys (Twitter, Claude, Ethereum RPC) fail silently or return errors.

• Environment variables appear undefined inside the app.

Solution:

• Confirm that your .env file is located at the root of the project (alongside package.json).

• Make sure all environment variable names exactly match those expected (TWITTER_API_KEY, CLAUDE_API_KEY, etc.).

• After modifying .env, stop and restart the development server. Vite does not reload .env files on the fly.

---

Port Conflict on Development Server

Symptoms:

• Running npm run dev or yarn dev results in an error like: Error: listen EADDRINUSE: address already in use :::3000

Solution:

• Identify and close the process occupying the port (e.g., another app, old dev server).

• Alternatively, start the dev server on a different port:

  npm run dev -- --port=4000

---

TypeScript Compilation Errors

Symptoms:

• Build or dev server fails due to TypeScript errors.

• Editor or terminal shows type mismatch or missing prop errors.

Solution:

• Make sure you’re running Node.js v16 or higher as required by the project.

• Run npm install or yarn install to ensure all dependencies and types are correctly installed.

• Verify that any custom components or modifications include proper TypeScript typings.

---

TailwindCSS Styles Not Applying

Symptoms:

• UI renders without expected Tailwind styling (no colors, spacing, or fonts).

• Console warnings about missing styles or content paths.

Solution:

• Verify tailwind.config.ts includes correct content paths:

  content: ['./src/**/*.{ts,tsx}'],

Confirm you have imported Tailwind base styles in your main CSS entry (usually index.css or main.css):

@tailwind base;
@tailwind components;
@tailwind utilities;

Restart the dev server after any Tailwind config changes.

---

If you encounter other issues or bugs not covered here, consider opening an issue in the project’s GitHub repository with detailed reproduction steps.