How to ship in CJS format when my package has pure ESM package dependencies?

index.ts:

import ora from 'ora'
 
const spinner = ora('Starting...').start()
spinner.succeed('Done!')

build.config.ts:

export default defineBuildConfig({
  entries: [
    'index',
  ],
  rollup: {
    emitCJS: true,
  },
})

run unbuild && node dist/index.cjs and get error:

const ora = require('ora');
            ^

Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/zhangjiawei/Desktop/git-download/node_modules/.pnpm/ora@6.1.0/node_modules/ora/index.js from /Users/zhangjiawei/Desktop/git-download/dist/index.cjs not supported.
Instead change the require of index.js in /Users/zhangjiawei/Desktop/git-download/dist/index.cjs to a dynamic import() which is available in all CommonJS modules.
    at Object.<anonymous> (/Users/zhangjiawei/Desktop/git-download/dist/index.cjs:3:13) {
  code: 'ERR_REQUIRE_ESM'
}

[holazz]

Anthony Fu helped me, I just needed to make execa a development dependency instead of a normal one, which completely makes sense!

So @holazz to solve the issue, use rollup.inlineDependencies and make your ESM-only dependency a development dependency.

Alternatively, as @pi0 said, find the same lib exported as CJS (ora v5.x), or finally, use dynamic imports.

Hopefully this solves the issue for anyone stumbling upon it.

Thank You Kindly! rollup.inlineDependencies should not be what I want, I am currently using the 5.x version of ora.

[innocenzi]

Anthony Fu helped me, I just needed to make execa a development dependency instead of a normal one, which completely makes sense!

So @holazz to solve the issue, use rollup.inlineDependencies and make your ESM-only dependency a development dependency.

Alternatively, as @pi0 said, find the same lib exported as CJS (ora v5.x), or finally, use dynamic imports.

Hopefully this solves the issue for anyone stumbling upon it.