Add .mts and .cts support to tailwind.config or respect parent's package.json when loading TypeScript configuration files.

[JessicaSachs]

Describe the feature

I cannot avoid these errors unless I change my Tailwind config to be JavaScript with an explicit extension (tailwind.config.mjs) even though my project has "type": "module" declared.

Is it possible to properly respect the projects package.json's type or otherwise support the official TypeScript file extensions that match their JavaScript parallels?

Additional information

• Would you be willing to help implement this feature?
• Could this feature be implemented as a module?

[JessicaSachs]

Workaround for some amount of Auto-complete support is to use JSDoc comments:

/**
 * See: https://github.com/nuxt-modules/tailwindcss/issues/902
 * @type { import("tailwindcss").Config }
 **/
export default {
  /* Autocomplete works within the configuration object */
}

[ineshbose]

Hi, thanks for opening this issue.

Regarding loading configuration, we use loadConfig from tailwindcss which uses jiti internally (but we may want to consider c12 for #808), and then for generating the configuration, we're still using CJS in the build directory (to be able to consistently require all syntaxes) - where would you be facing this issue?

Are we looking to add .mts, .cts here:

tailwindcss/src/resolvers.ts

Line 17 in e8e98de

.map(path => path.startsWith(nuxtOptions.buildDir) ? path : findPath(path, { extensions: ['.js', '.cjs', '.mjs', '.ts'] })),