As I see the code, adding "type":"module" to package.json resolved this, but it seems like a workaround. I suggest enhancing the extension to better handle different module definitions, improving flexibility and user experience.
Thanks for the suggestion.
I am not planning to support this since this is where JS development is headed. Using ESM "type":"module" will become the default.
I've encountered an issue related to the module parsing process #2 in the extension, specifically when integrating with Tailwind/PostCSS/Autoprefixer.
Initially, my configuration was as follows:
This setup functioned correctly. However, I encountered the following error after installing the extension:
After modifying the syntax with
export default
as suggested in the tailwind v3.3:The issue persists.
As I see the code, adding
"type":"module"
topackage.json
resolved this, but it seems like a workaround. I suggest enhancing the extension to better handle different module definitions, improving flexibility and user experience.Thank you for considering this suggestion.