vercel / vercel/next-learn

Unknown at rule @tailwindcss(unknownAtRules)

Open
#679 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
4.8k
Forks
2.2k
PR merge metrics
No merged PRs in 30d

Description

I found something wrong in app/ui/global.css, when i use eslint, it tells me that:
image
it turn out that @tailwind is not best practice, can anyone help me about this? and this is my postcss.config.js

// postcss.config.js
module.exports = {
  plugins: {
    tailwindcss: {},
    autoprefixer: {},
  },
};

this is my .lintstagerc.json, i can't make commits when i turn "eslint --fix" on, and i think this tutorial should be a best practice

// .lintstagerc.json
{
  "./app/**/*.{js,ts,jsx,tsx,json,html,css,md}": [
    "eslint --fix",
    "prettier --write"
  ]
}

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing app/ui/global.css alongside postcss.config.js and .lintstagerc.json to trace why ESLint reports @tailwind as an unknown at-rule. Run the configured eslint --fix and prettier --write commands, and consider the issue complete when the tutorial setup can commit without the reported diagnostic.

Written by the indexing model from the issue text.

Assessment

Tech stack
eslint, javascript, tailwindcss
Domain
frontend, tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.