Vercel deployment build issue, can't resolve components
Answered
SpicyJungle posted this in #help-forum
SpicyJungleOP
My project won't resovle a component that is a sibling to a different, similar component that resolves fine.
./src/app/dashboard/page.tsx
Module not found: Can't resolve '@/components/PremiumDashboardTab'@/components/PremiumDashboardTabexport default function PremiumDashboardTab({
guild,
}: {
guild: ExtendedGuild;
}) {
...
}./src/app/dashboard/page.tsx"use client";
import SettingsDashboardTab from "@/components/SettingsDashboardTab"; // resolves fine
...
import PremiumDashboardTab from "@/components/PremiumDashboardTab"; // errorAnswered by SpicyJungle
Fixed! For anyone with the same issue, I'm guessing it has to do with windows file system not being case sensitive, whereas linux and macos is, hence it works locally.
Since git won't track file name changes that only change capitalisation, you're gonna have to do it in two commits.
e.g:
non-tsx/ts files seems to be fine with capital letters though
Since git won't track file name changes that only change capitalisation, you're gonna have to do it in two commits.
e.g:
PremiumDashboardTab.tsx -> premiumdashboardtabx.tsx -> premiumdashboardtab.tsxnon-tsx/ts files seems to be fine with capital letters though
2 Replies
SpicyJungleOP
bumping this
SpicyJungleOP
Fixed! For anyone with the same issue, I'm guessing it has to do with windows file system not being case sensitive, whereas linux and macos is, hence it works locally.
Since git won't track file name changes that only change capitalisation, you're gonna have to do it in two commits.
e.g:
non-tsx/ts files seems to be fine with capital letters though
Since git won't track file name changes that only change capitalisation, you're gonna have to do it in two commits.
e.g:
PremiumDashboardTab.tsx -> premiumdashboardtabx.tsx -> premiumdashboardtab.tsxnon-tsx/ts files seems to be fine with capital letters though
Answer