Do not export default only from CJS packages, also because Typescript loose it's typenings

[frederikhors]

I really love ❤️ ViteJS.

What makes me sad is something like this below.

I wanna use the amazing https://github.com/Nozbe/WatermelonDB for a project but I have problems with ES/CJS music.

Since they are using CJS export today (I opened this asking for ES) I'm using this in my vite.config.js:

module.exports = {
  optimizeDeps: {
    include: [
      '@nozbe/watermelondb',
      '@nozbe/watermelondb/adapters/lokijs',
      '@nozbe/watermelondb/decorators'
    ]
  }
}

What makes me sad now is:

1. I cannot use this code:

   import { field } from '@nozbe/watermelondb/decorators'
   
     class Post extends Model {
     // ...
     @field('title') title
     @field('body') body
     // ... and so on
   }

   I need to use this instead:

   import allDecoratorsPackage from '@nozbe/watermelondb/decorators'
   
   class Post extends Model {
     // ...
     @allDecoratorsPackage.field('title') title
     @allDecoratorsPackage.field('body') body
     @allDecoratorsPackage.field('is_pinned') isPinned
     // ... and so on
   }

2. I loose Typescript definitions in case like this:

   import LokiJSAdapter from '@nozbe/watermelondb/adapters/lokijs'
   
   const adapter = new LokiJSAdapter.default({})

   and Typescript doesn't show definitions because of:

   Property 'default' does not exist on type 'typeof LokiJSAdapter'.ts(2339)
   

Given that sooner or later everyone will export ESM,

given that I am doing everything to speed up this process (flatpickr is almost done merging PR!),

can we please find a way for fix these two "issues" that hinder rapid application development?

Thank you for your talent and your time.

[antfu]

Please keep track on #720 & #837. Thanks for the feedback.