Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined when use cjs/mjs config about packemon HOT 8 CLOSED

I've created minimal reproduce
https://github.com/azu/packemon-cjs-issue

from packemon.

@azu Thanks, this should fix it #136

On a side note, I suggest not using cjs/mjs in parallel as you run the risk of the dual package hazard. https://nodejs.org/api/packages.html#dual-commonjses-module-packages I suggest one or the other, preferably cjs as packemon will automatically create an mjs wrapper. https://packemon.dev/docs/features#automatic-mjs-wrappers-for-cjs-inputs

from packemon.

Published, let me know if there's still issues.

from packemon.

from packemon.

I want to treat my package as mjs package by default(type: module) because We may need to migrate Pure ESM in the future. I think that commonjs support is optional.
In other words, I want to treat .ts as mjs.

By contrast, index-wrapper.mjs force type: "commonjs". so it treat my pacakge as cjs package by default.

from packemon.

@azu How does the index-wrapper.mjs force it to CJS?

from packemon.

@milesj
Reproduce repo: https://github.com/azu/packemon-cjs-and-mjs-wrapper

Reproduce Steps:

1. change type to "module" manually
2. npm run build
3. packemon will change type to "commonjs"

from packemon.

@azu The type is set based on the chosen format: https://github.com/milesj/packemon/blob/master/packages/packemon/src/Package.ts#L475 And since the format is cjs, it sets it.

It shouldn't matter though since the wrapper will be used when importing from ESM because the import exports is set in exports.

from packemon.