Possible to have `export default` emit as `module.exports`

I know it’s not the preferred way of having a default export, but it would save a lot of time if this would be possible. I’m writing an ESLint plugin and currently cannot import the plugin into a CJS file because the module is exported as module.exports.default rather than simply module.exports.

Have only come across this issue which I wasn’t able to find a way to implement it properly: https://github.com/egoist/tsup/issues/283 and also #255 but I got the warnings below:

Thanks!

[paambaati]

FWIW, I solved this by adding this to my tsup config –

import { defineConfig } from 'tsup'

export default defineConfig({
  splitting: false,
  sourcemap: false,
  minify: true,
  clean: true,
+  esbuildOptions: (options) => {
+   options.footer = {
+    // This will ensure we can continue writing this plugin
+      // as a modern ECMA module, while still publishing this as a CommonJS
+      // library with a default export, as that's how ESLint expects plugins to look.
+      // @see https://github.com/evanw/esbuild/issues/1182#issuecomment-1011414271
+      js: 'module.exports = module.exports.default;',
+    }
  },
  entry: ['src/index.ts'],
})

See https://github.com/getoslash/eslint-plugin-tap/pull/36 for reference.

[lvjiaxuan]

I know it’s not the preferred way of having a default export, but it would save a lot of time if this would be possible. I’m writing an ESLint plugin and currently cannot import the plugin into a CJS file because the module is exported as module.exports.default rather than simply module.exports.

Have only come across this issue which I wasn’t able to find a way to implement it properly: #283 and also #255 but I got the warnings below:

Thanks!

I am wondering why it's not the preferred way of having a default export. Could you explain any arguments for me, thanks~~