Repository navigation
question: is there a way to validate packages with mixed dual ESM/CJS and ESM-only subpackage exports? #241
Description
Activity
Right now, there’s no built-in way to change which checks “fail” the status (cause a non-zero exit code in the CLI) per-subpath. That’s something I’d like to improve in the future, but I don’t have time to actively add new features right now.
Reacted by Joaquín Sánchezyeah, that was my issue (thx):
You can still use
--profile esm-only, but it will apply across all subpaths.We use
cjs-resolves-to-esmat UnoCSS (attw configured to use the root json file here https://github.com/unocss/unocss/blob/main/.attw-esm-only.json), we have some extra checks after the build finish... I'll keep an eye to this issue, maybe if I have some time I can send a PR here.https://github.com/unocss/unocss/blob/main/scripts/dist-verify.ts
Reacted by Andrew Branch
For example, this simple one userquin/unbuild-cts-issue#1 or https://github.com/unocss/unocss/blob/main/packages-presets/unocss/package.json (https://arethetypeswrong.github.io/?p=unocss%4066.0.0).
I'm interested in the cli, we use
attrat UnoCSS.Thx for this great package.