Ship esm version

[tobiasdiez]

Currently, in the distributed/published version only commonjs is used. It would be nice if they would be also published as esm. This is needed for nuxt3/bridge, see nuxt-modules/tailwindcss#390 and https://v3.nuxtjs.org/concepts/esm#library-author-guide.

[rogden]

Thanks for the report. I'll need to dig into how to best do this. Might have to create a v2 and force node 12 instead of >=8. From my quick research it seems it can be quite a pain to manage both a cjs and esm version of a library.

[tobiasdiez]

Thanks for looking into this. Maintaining cjs + esm is indeed sadly not easy. The nuxt team developed https://github.com/unjs/unbuild that aims to help with this (I have no experience with this tool, but maybe its helpful).

[rogden]

As a quick fix so you can continue to use the viewer...you can turn it off in the Tailwind Nuxt Module config and then use it directly via npx tailwind-config-viewer assuming you have created a tailwind.config.js file in your Nuxt project root.

[DavidDeSloovere]

Is there still a need to support both cjs and esm? Maybe we can move forward with esm only.

[bkjohnson]

@rogden would you accept PR(s) to make this compatible with ESM tailwind configs? I'd be willing to help with that. Additionally, Node 18 is the lowest node version that isn't end of life, so a v2 release could include dropping unsupported node versions as well as a move to ESM compatibility.

[rogden]

@bkjohnson Absolutely!

[bkjohnson]

@rogden I opened #91 as a first step. I'm not a vue expert, but I'm assuming that being on the latest vue that uses vite will make it easier to ship a version with esm compatibility.

[rogden]

ESM support added in v2. Closing this out for now.

[ineshbose]

If I'm not wrong, this issue is more about the library moving to ESM syntax internally so possibly the surrounding ecosystem can also take advantage and benefit from it?

[tobiasdiez]

Supporting esm config files is nice, but I've opened this issue indeed with the wish to have a esm-version of the whole config-viewer package.

Could you please reopen the issue @rogden?

[ineshbose]

Supporting esm config files is nice, but I've opened this issue indeed with the wish to have a esm-version of the whole config-viewer package.

#92 seems to be fresher issue