build: update merger filename and revert @nuxt/content upgrade

[danielroe]

No description provided.

[what-the-diff]

PR Summary

• Introduction of a New Component
  We've introduced a new component to the software. This addition is expected to greatly enhance overall application functionality and user experience.

[netlify]

✅ Deploy Preview for nuxt-tailwindcss ready!

Name	Link
🔨 Latest commit	2fe53af
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt-tailwindcss/deploys/668071a3dac08f0008e38930
😎 Deploy Preview	https://deploy-preview-867--nuxt-tailwindcss.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[ineshbose]

Thanks for raising this PR but that TODO is what I have been wondering about, as the whole PostCSS/config may be in CJS syntax and/or Nuxt 2 projects may be in CJS. The MJS is explicit and helpful no? What shortcomings were there specifying that extension?

[danielroe]

The error is not coming from loading the merger.js file. Even when I update it to be .mjs, the same warnings are logged. I would not be surprised if it's a product of jiti loading tailwindcss or something similar. I believe you can reproduce with a fresh project using @nuxtjs/tailwindcss.

The main shortcoming is that *.mjs files require *.d.mts declarations for new TS bundler resolution as well as *.d.ts declarations for old TS resolution, meaning we have to emit twice as many files for backwards compatibility.

Also, this library is type: module so Node will always treat .js files in the project as ESM anyway.

And runtime/ files are mainly meant to be loaded by the build-time context which is always going to resolve them as ESM.

I would also add that supporting Nuxt 2 (with default behaviour) isn't a priority as it is EOL in a couple of days, though of course you can always revert the default extension to .mjs if you think it is important for this module.

[danielroe]

@ineshbose Seems we have a regression somewhere in that deps upgrade (though not, apparently, in the module-builder update)...

If you want to confirm that the .js extension isn't the cause of it, feel free to use the following build.config.ts (and rename merger.js -> merger.mjs):

import { defineBuildConfig } from 'unbuild'

export default defineBuildConfig({
  hooks: {
    'mkdist:entries'(ctx, entries) {
      entries[0].ext = 'mjs'
    }
  }
})

[ineshbose]

Thank you ❤️