René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"After updating to v22.12, always got ReferenceError: require is not defined in tailwind config","articleBody":"### Version\n\nv22.12.0\n\n### Platform\n\n```text\nDarwin Satriadhikaras-MacBook-Pro.local 24.1.0 Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:11 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6020 arm64\n```\n\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\nnpm run build on vite project that has already setup tailwindcss and shadcnui\n\n### How often does it reproduce? Is there a required condition?\n\nalways\n\n### What is the expected behavior? Why is that the expected behavior?\n\nbuild succeded\n\n### What do you see instead?\n\n$ tsc -b \u0026\u0026 vite build\r\n\r\n♻️  Generating routes...\r\n✅ Processed routes in 285ms\r\nvite v6.0.0 building for production...\r\ntransforming (1) src/main.tsxfile:///Users/......./tailwind.config.js:74\r\n        plugins: [require(\"tailwindcss-animate\")],\r\n                 ^\r\n\r\nReferenceError: require is not defined\r\n    at file:///Users/......./tailwind.config.js:74:11\r\n    at ModuleJobSync.runSync (node:internal/modules/esm/module_job:395:35)\r\n    at ModuleLoader.importSyncForRequire (node:internal/modules/esm/loader:329:47)\r\n    at loadESMFromCJS (node:internal/modules/cjs/loader:1414:24)\r\n    at Module._compile (node:internal/modules/cjs/loader:1547:5)\r\n    at Object..js (node:internal/modules/cjs/loader:1677:16)\r\n    at Module.load (node:internal/modules/cjs/loader:1318:32)\r\n    at Function._load (node:internal/modules/cjs/loader:1128:12)\r\n    at TracingChannel.traceSync (node:diagnostics_channel:322:14)\r\n    at wrapModuleLoad (node:internal/modules/cjs/loader:219:24)\r\n\r\nNode.js v22.12.0\n\n### Additional information\n\ni found this bug when i deploy it to vercel, but in my local it succeded built. and when i checked the node version of vercel it use v22.12.0, and at the time in my local i use v22.11.0. so when i update to the v22.12.0, it has the same error as vercel's build log. so i think the error is from v22.12.0","author":{"url":"https://github.com/satriadhikara","@type":"Person","name":"satriadhikara"},"datePublished":"2024-12-05T03:02:39.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/56140/node/issues/56140"}