Errors during deployment; tailwind.config.js module not defined

[kwame360]

ReferenceError: module is not defined

at file:///vercel/path0/tailwind.config.js:2:1

at ModuleJobSync.runSync (node:internal/modules/esm/module_job:395:35)

at ModuleLoader.importSyncForRequire (node:internal/modules/esm/loader:329:47)

at loadESMFromCJS (node:internal/modules/cjs/loader:1414:24)

at Module._compile (node:internal/modules/cjs/loader:1547:5)

at Object…js (node:internal/modules/cjs/loader:1677:16)

at Module.load (node:internal/modules/cjs/loader:1318:32)

at Function._load (node:internal/modules/cjs/loader:1128:12)

at TracingChannel.traceSync (node:diagnostics_channel:322:14)

at wrapModuleLoad (node:internal/modules/cjs/loader:219:24)

[pawlean (Pauline P. Narvas)]

Hi, @kwame360! Welcome to the Vercel Community

Without seeing your code, it’s difficult to help out here. But we do have a community post on how to debug these kinds of errors! Hopefully it’s helpful

Debugging Build Errors

When deploying your project on Vercel, you might encounter build errors that prevent your site from going live. Here are some ways to identify common issues and steps to resolve them. Analyzing the Build Log The first step in debugging is to carefully examine the build log. Look for these common issues: NPM Package Errors Update Required: If you see messages about outdated packages, try updating them in your package.json file. Legacy Peer Dependencies: For errors related to peer dependenci…

[hithesh98 (tesh)]

I have the same issue. Posted here Build Works Locally but Fails in Vercel Production - #10 by hithesh98