You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see in the screenshot, I get an error when adding prefix & defaultFlavour to the tailwind config:
Type error: This expression is not callable.
Type 'typeof import("/opt/repos/projects/portfolio/node_modules/.pnpm/@catppuccin+tailwindcss@0.1.6_tailwindcss@3.4.1/node_modules/@catppuccin/tailwindcss/dist/index")' has no call signatures.
When removing the prefix & defaultFlavour, it works..
The text was updated successfully, but these errors were encountered:
This is not related to Next.js. You can simply make a foo.js file with this content
// @ts-checkconstfoo=require("@catppuccin/tailwindcss");foo({});// TS errorfoo.default({});// TS is happy
to reproduce the error.
From a quick glance, the cause seems to be that @catppuccin/tailwindcss should've used export = instead of export default.
What you can do right now while waiting for this bug to be patched: use tailwind.config.ts instead where you can use ESM syntax
// tailwind.config.tsimporttype{Config}from"tailwindcss";importtailwindFormsfrom"@tailwindcss/forms";importcatppuccinfrom"@catppuccin/tailwindcss";constconfig: Config={content: ['./app/**/*.{js,ts,jsx,tsx}','./components/**/*.{js,ts,tsx}','.css/**/*.css'],theme: {},safelist: [// this is for demonstration purposes only, not required for basic usage{pattern: /bg-.+/,},],plugins: [tailwindForms,catppuccin({prefix: 'one',defaultFlavour: 'mocha',}),],};exportdefaultconfig;
As you can see in the screenshot, I get an error when adding prefix & defaultFlavour to the tailwind config:
Type error: This expression is not callable.
Type 'typeof import("/opt/repos/projects/portfolio/node_modules/.pnpm/@catppuccin+tailwindcss@0.1.6_tailwindcss@3.4.1/node_modules/@catppuccin/tailwindcss/dist/index")' has no call signatures.
When removing the prefix & defaultFlavour, it works..
The text was updated successfully, but these errors were encountered: