Skip to content

Feature: Redundant Content Resolution Path in tailwind.config.js#693

Open
Kirtan-pc wants to merge 1 commit into
Coder-s-OG-s:mainfrom
Kirtan-pc:redundant-content-resolution
Open

Feature: Redundant Content Resolution Path in tailwind.config.js#693
Kirtan-pc wants to merge 1 commit into
Coder-s-OG-s:mainfrom
Kirtan-pc:redundant-content-resolution

Conversation

@Kirtan-pc

Copy link
Copy Markdown
Contributor

Summary

Tailwind config content array includes dead/non-existent file extensions (*.js, *.jsx, *.mdx) in its scan paths, causing redundant filesystem operations during development builds.

Type of Change

  • Bug fix
  • New feature
  • UI / UX improvement
  • Refactor
  • Documentation
  • Other

Related Issue

Closes #672

What was changed?

tailwind.config.js — Narrowed glob extensions from {js,ts,jsx,tsx,mdx} to {ts,tsx} in both content paths, since the project uses TypeScript exclusively (src/ contains zero .js, .jsx, or .mdx files).

Checklist

  • My code follows the project structure and conventions
  • I tested this locally (npm run dev)
  • No hardcoded secrets or credentials
  • I have updated documentation if needed

@vercel

vercel Bot commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

@Kirtan-pc is attempting to deploy a commit to the codersogs-3057's projects Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEATURE] - Redundant Content Resolution Path in tailwind.config.js

1 participant