-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibility with NodeJS 23.1.0 #14818
Comments
Renaming |
This is because Node.js 23 unflagged Imho, tailwindcss should just use |
Yep. Doing this fixed the problem for me: - const colors = require("tailwindcss/colors");
+ import colors from "tailwindcss/colors" What are the implications of this change? Why isn't this the recommended approach in the first place? |
Running in SvelteKit I found I needed to rename
|
Tailwind CSS: (node:12872) ExperimentalWarning: CommonJS module C:\Program Files\JetBrains\PhpStorm 2024.2.4\plugins\tailwindcss\server\tailwindcss-language-server is loading ES Module c:\Herd\donavisos\tailwind.config.js using require(). Support for loading ES Module in require() is an experimental feature and might change at any time (Use |
(node:83498) ExperimentalWarning: CommonJS module /node_modules/tailwindcss/lib/lib/load-config.js is loading ES Module /resources/css/filament/admin/tailwind.config.js using require(). |
I encountered the same issue. I solved it by renaming |
What version of Tailwind CSS are you using?
3.4.14
What build tool (or framework if it abstracts the build tool) are you using?
Angular 18
What version of Node.js are you using?
23.1.0
What browser are you using?
N/A
What operating system are you using?
ArchLinux
Reproduction URL
Not needed
Describe your issue
While building my app I got following bug:
(node:341900) ExperimentalWarning: CommonJS module /home/alexander/Dev/angular/moem/node_modules/tailwindcss/lib/lib/load-config.js is loading ES Module /home/alexander/Dev/angular/moem/tailwind.config.js using require(). Support for loading ES Module in require() is an experimental feature and might change at any time
thus my config is not imported. The bug affects only NodeJS 23.1.0 which is default now in ArchLinux. Downgrading to NodeJS LTS fixes the issue.
The text was updated successfully, but these errors were encountered: