Hi. I was curious if the main field was not included purposefully? It seems to be causing issues with typescript@next's ESM handling, as it is a little more strict on where it looks for types. That is experimental behaviour so I just wanted to open the discussion of adding a main field as that should not cause issues for CJS or ESM but will fix the type resolution from ora when using typescript@next alonside the new "module": "nodenext" option.