rewrite-default-exports v1.0.7

rewrite-default-exports

It is codemod to rewrite your default exports to named ones and replace old names across your codebase.

Motivation

One day you might think about using named import and named export instead of default import and default export because it is a well-known best practice. After that you can add eslint rule for prohibiting export default in your code base with eslint/no-default-export or biomejs/no-default-export.

How to use it

Step 1: Gather Information

Run the following to collect default imports/exports:

IS_GATHER_INFO=true ENTRY="./path/to/your/entry.js" npx rewrite-default-exports

Step 2: Transform Imports/Exports

IS_TRANSFORM=true ENTRY="./path/to/your/entry.js" npx rewrite-default-exports

It uses jscodeshift (with babel inside) to transform files and the resolve package to resolve all imports. It will collect all relations between files and will transform all default imports and exports to named exports.

How to run and see the result as an example

1. download this repo
2. run yarn
3. add .env file to the root with:

DEBUG_APP=true - to see debug logs, by default it is false
ENTRY=./packages/app/client.js - entry file to gather info from
IS_GATHER_INFO=true - to gather info
IS_TRANSFORM=false - to transform files

4. run yarn transform
5. you will see generated files in src/dump folder

defaultImports.json - info about files having used default import
exportsNames.json - info about files having used default export
preservedDefaultExports.json - info about files having been imported via dynamic import
proxyDefaultExports.json - info about files having used default import and having re-exported them with default export

6. change in your .env file:

IS_GATHER_INFO=false
IS_TRANSFORM=true

7. run yarn transform
8. you will see transformed files in packages folder

Limitations

1. namespace.default usage this won't be transformed yet:

   import * as allConst from './test-te-const';
   console.log(allConst.default);

2. Conflicts in proxy files:
   1. source

   export { Modals as default } from './Modals';
   export { Modals } from './Modals';

   2. result

   export { Modals } from './Modals';
   export { Modals } from './Modals';

3. Messed exports like:
   1. source

   export class GhostDataProvider {}
   export default hoc()(GhostDataProvider);

   2. will result in broken logic, because now it has two same exports with different implementation

   export class GhostDataProvider {}
   const GhostDataProviderAlias = hoc()(GhostDataProvider);
   export { GhostDataProviderAlias as GhostDataProvider };

   3. and imports for the entity should be fixed manually too
      1. source

      // was used to get the class without HOC
      import { GhostDataProvider } from '.'
      ...
      // was used to get the class with HOC
      import GhostDataProvider from '.'

      2. result

      // now you should manually resolve it to class without HOC somehow
      import { GhostDataProvider } from '.'
      ...
      // this will get the class with the HOC
      import { GhostDataProvider } from '.'

Links

• jscodeshift
• astexplorer