Open xeho91 opened 1 year ago
Hi, thanks for opening this. Typewind currently directly imports the tailwind config, so it being in ts causes an error. Should be an easy fix, will look into it
Converting the Tailwind configuration file name to tailwind.config.cjs
and adapting the code to common JS:
/** @type {import('tailwindcss').Config} */
// eslint-disable-next-line no-undef
module.exports = {
content: ["./src/**/*.{html,js}"],
theme: {
extend: {},
},
plugins: [],
};
fixes it
Hey there, I'm looking into using typewind and I also have a .ts
tailwind config file, am I correct to assume this is still a problem since there have been no further updates here and the issue is still open?
Sorry, yeah this is still a problem. I'll try getting to it this weekend!
Hi,
thank you for this fantastic tool :heart:
In the version
3.3
of Tailwind CSS, they added a support for ESM and TypeScript config.I've changed my config to ESM, and rename it to
tailwind.config.ts
. I am trying to generate the types with the following command:then I get the following error:
Additional information
My project has
type
set tomodule
inpackage.json
file.