chore: Fix node v22 compatibility by converting Tailwind config to ESM #133
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prerequisites checklist
What is the purpose of this pull request?
This PR resolves a ReferenceError: module is not defined error that occurs when running the application on Node.js v22. The error was caused by a module system mismatch where the project uses ES modules ("type": "module" in package.json) but the Tailwind config file was using CommonJS syntax, which Node.js v22 enforces more strictly than previous versions.
What changes did you make? (Give an overview)
Converted
tailwind.config.jsfrom CommonJS to ES module syntax:1,. Changed export syntax: Replaced module.exports = { with export default {
2. Updated import syntax: Replaced require("tailwindcss-animate") with import tailwindcssAnimate from "tailwindcss-animate"
This change ensures compatibility with Node.js v22+ while maintaining backward compatibility with earlier versions, and aligns the configuration with the project's ES module setup.
Related Issues
Is there anything you'd like reviewers to focus on?