Named export vs Default export about meilisearch-js-plugins HOT 2 CLOSED

Thanks for the detailed overview! It was not my intention to trigger that much work with my seemingly small question. Sorry.

To elaborate my vote in favor of named exports, some additional comments:

• Regarding Pro-default 2

  I think this argument is a bit historic as default was the earlier option. I think this point should be removed from the list or even be moved to the con-default list. Here's why:

  where you can change the name

  You can also rename named exports like e.g. import { instantMeiliSearch as whatIWant } from 'instant-meilisearch'. Refactoring would then rename instantMeiliSearch but not the local name whatIWant.

  Also, given the package is already installed, with Named exports I could just type instantM (or even less), get the autocompletion (from vscode, in my case) which then automatically adds a named import (or extends an existing one, if something else from the package was already imported).

  If I'm missing the import but have a snippet pasted from somewhere like basic usage example from the readme, it would underline the method name and provide the autofix to add a named import. I think it does not do that for default exports (at least it didn't for axios which I just tried it with.)

  Concluding this bullet, I'd consider named exports easier to use than default and would just cross that point from the pro-list.

• Another con-default:

  If there's a reason later to export another function, this would be very easy with named exports, but not with default exports.

• Another pro-default:

  • changing it now would be breaking change (but the earlier, the better?)

Here's another list of arguments against default export (some of which have already been mentioned), from @basarat's book TypeScript Deep Dive: https://basarat.gitbook.io/typescript/main-1/defaultisbad

from meilisearch-js-plugins.

Closed by: #238

from meilisearch-js-plugins.