Config is forced as CJS and forbid usage of `import.meta`

[ArnaudBarre]

What version of VS Code are you using?

For example: v1.104.2

What version of Tailwind CSS IntelliSense are you using?

For example: v0.14.26

What version of Tailwind CSS are you using?

For example: v3.4.17

What package manager are you using?

For example: bun

What operating system are you using?

For example: macOS

Tailwind CSS Stylesheet (v4) or config file (v3)

v3 config file

console.log(import.meta.filename);

export default {};

Describe your issue

It seems that jiti is always transforming to cjs despite my package.json being "type": "module".
Reproduced with a Vite starter

[thecrypticace]

So this should be addressed by tailwindlabs/tailwindcss#18938 but it will only work if require(esm) is supported. afaik your vscode version is new enough so this should be fixed once we tag Tailwind CSS v3.4.18.

[ArnaudBarre]

Oh yeah I didn't look into the issues in the tailwind repo
I found a workaround, but happy to drop it once released!

[ArnaudBarre]

Side question: would you release an update of the extension that bundles the latest versions so it also works when tailwind is not installed?

[thecrypticace]

Yeah, I am planning to do that for this project and for our prettier plugin as well.