#Description-
-According to the architecture overview of the MergeShip platform, the project structure utilizes the modern Next.js App Router setup where application-level views, pages, and components reside strictly within the src/app/ and src/components/ directories.
The current configuration includes ./src/pages/**/*.{js,ts,jsx,tsx,mdx} inside the configuration's content array. Because MergeShip relies entirely on the Next.js App Router (src/app), tracking file changes under a non-existent src/pages folder forces Tailwind CSS to scan redundant structures during development compilation passes.
Solution -
Clean up the utility scanning array paths to mirror the repository's concrete design pattern by omitting the dead path entry, improving build performance.
#Description-
-According to the architecture overview of the MergeShip platform, the project structure utilizes the modern Next.js App Router setup where application-level views, pages, and components reside strictly within the src/app/ and src/components/ directories.
The current configuration includes ./src/pages/**/*.{js,ts,jsx,tsx,mdx} inside the configuration's content array. Because MergeShip relies entirely on the Next.js App Router (src/app), tracking file changes under a non-existent src/pages folder forces Tailwind CSS to scan redundant structures during development compilation passes.
Solution -
Clean up the utility scanning array paths to mirror the repository's concrete design pattern by omitting the dead path entry, improving build performance.