Incorrect Tailwind config

Open
#19 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
next.js, tailwindcss
Domain
frontend

Research direction

Open tailwind.config.js and inspect the content paths used for the Next app. Update the configuration to cover the app folder as described in the issue, then verify that Tailwind styling is generated for files under app.

Written by the indexing model from the issue text.

Description

I won't fork for such a small change.

Your tailwind.config.js is pointing to the pages folder, but you are implementing next's experimental app folder so no tailwind styling is being generated.

(...)
content: [
    "./pages/**/*.{js,ts,jsx,tsx}",
    (...)

Should be

(...)
content: [
    "./app/**/*.{js,ts,jsx,tsx}",
    (...)
Dominant language
TypeScript
Stars
104
Forks
37
No merged PRs in 30d

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.

More from contentlayerdev/next-contentlayer-example

All issues in contentlayerdev/next-contentlayer-example

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.