\n\n \n\n# babel-plugin-transform-rewrite-imports\n\n\n\nThis Babel plugin (1) reliably adds [_extensions_][1] to import and export\n[_specifiers_][2] that do not already have one, (2) selectively replaces\nextensions of specifiers that do, and (3) can rewrite whole specifiers in\nintricate ways using simple yet powerful [replacement maps][3].\n\nAll TypeScript and JavaScript flavors are supported depending on how Babel is\nconfigured in the project.\n\nFor example, something like this:\n\n```typescript\nimport { item1, type item2 } from '==> pretty specifier #1 <==';\n\nexport { here as there } from '==> pretty specifier #2 <==';\n\nconst elsewhere = `==> pretty specifier #${getRandomNumber()} <==`;\n\njest.mock('==> pretty specifier #3 <==');\n\nconst x = require('==> pretty specifier #4 <==');\n\nexport async function myFunction() {\n return (await import(elsewhere, { with: { type: 'json' } })).name;\n}\n\nexport type MyType = {\n typeOnlyImport: typeof import('==> pretty specifier #5 <==').Type;\n};\n```\n\nCan be easily transformed into something like this:\n\n```typescript\nimport { item1, type item2 } from '../../../specifier-1.js';\n\nexport { here as there } from '../specifier-2.js';\n\nconst elsewhere = `==> specifier #${getRandomNumber()} <==`;\n\njest.mock('../../../packages/a-different-monorepo-package/src/specifier-3.js');\n\nconst x = require('@specifier/four');\n\nconst __injected_dynamic_rewrite = function () {\n /*...*/\n};\n\nexport async function myFunction() {\n return (\n await import(__injected_dynamic_rewrite(elsewhere), {\n with: { type: 'json' }\n })\n ).name;\n}\n\nexport type MyType = {\n typeOnlyImport: typeof import('../../../../node_modules/s-5/dist/src/lib.d.ts').Type;\n};\n```\n\nThe transform-rewrite-imports plugin comes in handy in situations like\ntranspiling TypeScript source with extensionless imports to ESM, or [changing\nalias paths][4] in TypeScript declaration (i.e. `.d.ts`) files into relative\npaths suitable for publishing. It does this more reliably and efficiently than\nprior art.\n\n\n\n---\n\n\n\n\n\n\n- [Install](#install)\n- [Comparison with Prior Art](#comparison-with-prior-art)\n- [Usage](#usage)\n - [`appendExtension`](#appendextension)\n - [`recognizedExtensions`](#recognizedextensions)\n - [`replaceExtensions`](#replaceextensions)\n - [`requireLikeFunctions`](#requirelikefunctions)\n - [`injectDynamicRewriter`](#injectdynamicrewriter)\n- [Advanced Usage](#advanced-usage)\n - [Rewriting Dynamic Imports and Requires with Non-Literal Arguments](#rewriting-dynamic-imports-and-requires-with-non-literal-arguments)\n- [Comprehensive Logging](#comprehensive-logging)\n- [Examples](#examples)\n - [Real-World Examples](#real-world-examples)\n- [Appendix](#appendix)\n - [Published Package Details](#published-package-details)\n - [License](#license)\n- [Contributing and Support](#contributing-and-support)\n - [Contributors](#contributors)\n\n\n\n\n\n \n\n## Install\n\n\n\n```shell\nnpm install --save-dev babel-plugin-transform-rewrite-imports\n```\n\nAnd integrate the following snippet into your Babel configuration:\n\n```typescript\nmodule.exports = {\n plugins: [\n [\n 'babel-plugin-transform-rewrite-imports',\n {\n // See below for configuration instructions and examples\n }\n ]\n ]\n};\n```\n\nFinally, run Babel through your toolchain (Webpack, Jest, etc) or manually:\n\n```shell\nnpx babel src --out-dir dist\n```\n\n## Comparison with Prior Art\n\nThe transform-rewrite-imports plugin effectively combines the functionality of\nthe following:\n\n- [babel-plugin-module-resolver][5]\n\n The module-resolver plugin inspired quite a bit of the functionality of\n transform-rewrite-imports, such as [transforming `require`-like functions][6],\n and offers some similar features like RegExp-based aliasing and support for\n substitution functions. However, transform-rewrite-imports is capable of more\n complex replacements (like handling intricate file extension changes) with\n support for a wider variety of specifier types while surfacing a simpler\n interface.\n\n- [babel-plugin-add-import-extension][7]\n\n transform-rewrite-imports started off as a fork of add-import-extension;\n transform-rewrite-imports functions [more consistently][8] and includes\n support for transforming `require`, `require`-like, static `import()`, _and\n arbitrary dynamic `import()`_ statements, replacing multiple extensions using\n complex logic, and [reliably ignoring extensions that should not be\n replaced][9].\n\n- [babel-plugin-replace-import-extension][10]\n\n transform-rewrite-imports is similar in intent to replace-import-extension.\n However, rewriting extensions is only a small fraction of what\n transform-rewrite-imports can do. And while both extensions support\n [transforming dynamic imports][11], transform-rewrite-imports results in more\n efficient code in production environments due to (1) avoiding injecting\n dynamic code into the AST except as the very last resort and (2) only\n injecting dynamic code once and caching it globally (at the file level) rather\n than filling the file with repeated functions.\n\n- [babel-plugin-transform-rename-import][12]\n\n With its last update published over 6 years ago, transform-rename-import can\n also replace import specifiers, though transform-rewrite-imports offers a\n [powerful superset][13] of replacer functionality, including optionally\n performing replacements of [arbitrary dynamic imports][11] at runtime and\n appending extensions to specifiers that would otherwise not have one.\n\n- [tsconfig-replace-paths][14] / [tsconfig-paths][15] / [tscpaths][16]\n\n tsconfig-replace-paths and its predecessors/alternatives tsconfig-paths and\n tscpaths are extremely useful for transpiling TypeScript projects, as they\n handle alias- and path- resolving use cases without additional configuration;\n transform-rewrite-imports, on the other hand, must be fed path/alias\n information from `tsconfig.json` manually.\n\n Unfortunately, tsconfig-paths is not a Babel plugin and requires [patching\n your runtime][17] while the others do not support all the latest\n TypeScript/Babel AST features (like [`TsImportType`][18]) and therefore fail\n to consistently and correctly transform certain files (especially certain\n `.d.ts` files).\n\n By mapping a project's `tsconfig.json` `paths` value to a replacement map\n transform-rewrite-imports can understand, it becomes possible to ditch\n tsconfig-replace-paths etc and reduce dependency count. [Here's an\n example][19] using transform-rewrite-imports to replace these plugins (and\n babel-plugin-module-resolver) for transforming both sources and type\n definitions. Essentially, this Babel configuration file maps the project's\n `tsconfig.json` `paths` into a [`replaceExtensions`][13] replacement map.\n\n## Usage\n\nBy default this plugin does not affect Babel's output. You must explicitly\nconfigure this extension before any specifier will be rewritten.\n\nMore information on the available options can be found in [the\ndocs][x-repo-docs]:\n\n```typescript\n{\n appendExtension?: string | Callback;\n recognizedExtensions?: string[];\n replaceExtensions?: Record>;\n requireLikeFunctions?: string[];\n injectDynamicRewriter?: 'never' | 'only-if-necessary';\n silent?: boolean;\n verbose?: boolean;\n}\n```\n\n### `appendExtension`\n\nTo append an extension to all relative import specifiers that do not already\nhave a recognized extension, use `appendExtension`:\n\n```typescript\nmodule.exports = {\n plugins: [\n [\n 'babel-plugin-transform-rewrite-imports',\n {\n appendExtension: '.mjs'\n }\n ]\n ]\n};\n```\n\n> [!TIP]\n>\n> Only relative import specifiers (that start with `./` or `../`) will be\n> considered for `appendExtension`. This means bare specifiers (e.g. built-in\n> packages and packages imported from `node_modules`) and absolute specifiers\n> will never be affected by `appendExtension`.\n\n### `recognizedExtensions`\n\nWhat is and is not considered a \"recognized extension\" is determined by\n`recognizedExtensions`:\n\n```typescript\nmodule.exports = {\n plugins: [\n [\n 'babel-plugin-transform-rewrite-imports',\n {\n appendExtension: '.mjs',\n recognizedExtensions: ['.js']\n }\n ]\n ]\n};\n```\n\nThat is: **import specifiers that end with an extension included in\n`recognizedExtensions` will never have [`appendExtension`][21] appended to\nthem**. All other imports, including those with a `.` in the file name (e.g.\n`component.module.style.ts`), may be rewritten.\n\n`recognizedExtensions` is set to `['.js', '.jsx', '.mjs', '.cjs', '.json']` by\ndefault.\n\nIf the value of [`appendExtension`][21] is not included in\n`recognizedExtensions`, then imports that already end in [`appendExtension`][21]\nwill have [`appendExtension`][21] appended to them (e.g. `index.ts` is rewritten\nas `index.ts.ts` when `appendExtension: '.ts'` and `recognizedExtensions` is its\ndefault value). If this behavior is undesired, ensure [`appendExtension`][21] is\nincluded in `recognizedExtensions`.\n\n> [!WARNING]\n>\n> Note that specifying a custom value for `recognizedExtensions` overwrites the\n> default value entirely. To extend rather than overwrite, you can import the\n> default value from the package itself:\n>\n> ```typescript\n> const {\n> defaultRecognizedExtensions\n> } = require('babel-plugin-transform-rewrite-imports');\n>\n> module.exports = {\n> plugins: [\n> [\n> 'babel-plugin-transform-rewrite-imports',\n> {\n> appendExtension: '.mjs',\n> recognizedExtensions: [...defaultRecognizedExtensions, '.ts']\n> }\n> ]\n> ]\n> };\n> ```\n\n### `replaceExtensions`\n\nYou can also replace one or more existing extensions in specifiers using a\nreplacement map:\n\n```typescript\nmodule.exports = {\n plugins: [\n [\n 'babel-plugin-transform-rewrite-imports',\n {\n replaceExtensions: {\n // Replacements are evaluated **in order**, stopping on the first match.\n // That means if the following two keys were listed in reverse order,\n // .node.js would become .node.mjs instead of .cjs\n '.node.js': '.cjs',\n '.js': '.mjs'\n }\n }\n ]\n ]\n};\n```\n\nThese configurations can be combined to rewrite many imports at once. For\ninstance, if you wanted to replace certain extensions and append only when no\nrecognized or listed extension is specified:\n\n```typescript\nmodule.exports = {\n plugins: [\n [\n 'babel-plugin-transform-rewrite-imports',\n {\n appendExtension: '.mjs',\n replaceExtensions: {\n '.node.js': '.cjs',\n // Since .js is in recognizedExtensions by default, file.js would normally\n // be ignored. However, since .js is mapped to .mjs in the\n // replaceExtensions map, file.js becomes file.mjs\n '.js': '.mjs'\n }\n }\n ]\n ]\n};\n```\n\nSince specifier comparisons are made using [`String.endsWith`][39] without\nsplitting on directory separators or any other characters,\n[`appendExtension`][21] and `replaceExtensions` accept any suffix, not just\nthose that begin with `.`; additionally, `replaceExtensions` accepts _regular\nexpressions_. This allows you to partially or entirely rewrite a specifier\nrather than just its extension:\n\n```typescript\nconst {\n defaultRecognizedExtensions\n} = require('babel-plugin-transform-rewrite-imports');\n\nmodule.exports = {\n plugins: [\n [\n 'babel-plugin-transform-rewrite-imports',\n {\n appendExtension: '.mjs',\n // Add .css to recognizedExtensions so .mjs isn't automatically appended\n recognizedExtensions: [...defaultRecognizedExtensions, '.css'],\n replaceExtensions: {\n '.node.js': '.cjs',\n '.js': '.mjs',\n\n // The following key replaces the entire specifier when matched\n '^package$': `${__dirname}/package.json`,\n // If .css wasn't in recognizedExtensions, my-utils/src/file.less would\n // become my-utils/src/file.css.mjs instead of my-utils/src/file.css\n '(.+?)\\\\.less$': '$1.css'\n }\n }\n ]\n ]\n};\n```\n\n> [!TIP]\n>\n> If a key of `replaceExtensions` begins with `^` _or_ ends with `$`, it is\n> considered a regular expression instead of an extension. Regular expression\n> replacements support substitutions of capturing groups as well (e.g. `$1`,\n> `$2`, etc).\n\n`replaceExtensions` is evaluated and replacements made _before_\n[`appendExtension`][21] is appended to specifiers with unrecognized or missing\nextensions. This means an extensionless import specifier could be rewritten by\n`replaceExtensions` to have a recognized extension, which would then be ignored\ninstead of having [`appendExtension`][21] appended to it.\n\n### `requireLikeFunctions`\n\nWhen it comes to deciding what is and is not a specifier,\ntransform-rewrite-imports will always scan [`ImportDeclaration`][22],\n[`ExportAllDeclaration`][23], [`ExportNamedDeclaration`][24],\n[`TSImportType`][18], and dynamic import [`CallExpression`][25]s for specifiers.\n\nFor call expressions specifically, `requireLikeFunctions` is used to determine\nwhich additional function calls will have their first arguments scanned for\nspecifiers. By default, `requireLikeFunctions` is set to:\n\n```typescript\n[\n 'require',\n 'require.resolve',\n 'System.import',\n 'jest.genMockFromModule',\n 'jest.mock',\n 'jest.unmock',\n 'jest.doMock',\n 'jest.dontMock',\n 'jest.requireActual'\n];\n```\n\n> [!TIP]\n>\n> Similar to `defaultRequireLikeFunctions`, these defaults are exported under\n> the name `defaultRequireLikeFunctions`.\n\nThis means call expressions like `require(...)`, `jest.mock(...)`, etc will be\ntreated the same way as `import(...)`, where the first parameter is considered a\nspecifier. You are free to tweak this functionality to suit your environment.\n\n### `injectDynamicRewriter`\n\nBy default, a dynamic rewriter is injected only if necessary. Set this to\n`\"never\"` to ensure a dynamic rewriter is _never_ injected into the the output\nregardless of any perceived necessity.\n\nRefer to [the Advanced Usage section][11] for more details.\n\n## Advanced Usage\n\n[`replaceExtensions`][13] and [`appendExtension`][21] both accept function\ncallbacks as values everywhere strings are accepted. This can be used to provide\nadvanced replacement logic.\n\nThese callback functions have the following signatures:\n\n```typescript\ntype AppendExtensionCallback = (context: {\n specifier: string;\n capturingGroups: never[];\n filepath: string;\n}) => string | undefined;\n\ntype ReplaceExtensionsCallback = (context: {\n specifier: string;\n capturingGroups: string[];\n filepath: string;\n}) => string;\n```\n\nWhere `specifier` is the [import/export specifier][2] being rewritten,\n`capturingGroups` is a simple string array of capturing groups returned by\n[`String.prototype.match()`][26], and `filepath` is the absolute path to the\noriginal input file being transformed by Babel. `capturingGroups` will always be\nan empty array except when it appears within a function value of a\n[`replaceExtensions`][13] entry that has a regular expression key.\n\nWhen provided as the value of [`appendExtension`][21], a string containing an\nextension should be returned (including leading dot). When provided as the value\nof a [`replaceExtensions`][13] entry, a string containing the full specifier\nshould be returned. When returning a full specifier, capturing group\nsubstitutions (e.g. $1, $2, etc) within the returned string will be honored.\n\nFurther, in the case of [`appendExtension`][21], note that `specifier`, if its\nbasename is `.` or `..` or if it ends in a directory separator (e.g. `/`), will\nhave \"/index\" appended to the end before the callback is invoked. However, if\nthe callback returns `undefined` (and the specifier was not matched in\n[`replaceExtensions`][13]), the specifier will not be modified in any way.\n\nBy way of example (see the output of this example [here][27]):\n\n```typescript\nmodule.exports = {\n plugins: [\n [\n 'babel-plugin-transform-rewrite-imports',\n {\n // If the specifier ends with \"/no-ext\", do not append any extension\n appendExtension: ({ specifier }) => {\n return specifier.endsWith('/no-ext') ||\n specifier.endsWith('..') ||\n specifier === './another-thing'\n ? undefined\n : '.mjs';\n },\n replaceExtensions: {\n // Rewrite imports of packages in a monorepo to use their actual names\n // v capturing group #1: capturingGroups[1]\n '^packages/([^/]+)(/.+)?': ({ specifier, capturingGroups }) => {\n // ^ capturing group #2: capturingGroups[2]\n if (\n specifier === 'packages/root' ||\n specifier.startsWith('packages/root/')\n ) {\n return `./monorepo-js${capturingGroups[2] ?? '/'}`;\n } else if (\n !capturingGroups[2] ||\n capturingGroups[2].startsWith('/src/index')\n ) {\n return `@monorepo/$1`;\n } else if (capturingGroups[2].startsWith('/package.json')) {\n return `@monorepo/$1$2`;\n } else {\n return `@monorepo/$1/dist$2`;\n }\n }\n }\n }\n ]\n ]\n};\n```\n\n### Rewriting Dynamic Imports and Requires with Non-Literal Arguments\n\nWhen transforming dynamic imports and require statements [that do not have a\nstring literal as the first argument][28], and [`injectDynamicRewriter`][20] is\nnot set to `'never'`, the options passed to this plugin are [transpiled and\ninjected][30] into the resulting AST.\n\n> [!CAUTION]\n>\n> This means you take a slight performance hit when you do arbitrary dynamic\n> imports that cannot be statically analyzed (e.g.\n> `require(getMd5Hash() + '.txt')`). These types of dynamic imports are usually\n> code smell, but this library is built to accommodate them regardless.\n>\n> However, **if you are NOT doing _arbitrary_ dynamic imports**, which are\n> dynamic imports where the first argument is not a string literal, then this\n> section is of no relevance to you since nothing extra will be injected into\n> the AST.\n\nTherefore, to be safe, **callback functions must not reference variables outside\nof their immediate [scope][31]**.\n\nGood:\n\n```typescript\nmodule.exports = {\n plugins: [\n [\n 'babel-plugin-transform-rewrite-imports',\n {\n replaceExtensions: {\n '^packages/([^/]+)(/.+)?': ({ specifier, capturingGroups }) => {\n const myPkg = require('my-pkg');\n myPkg.doStuff(specifier, capturingGroups);\n }\n }\n }\n ]\n ]\n};\n```\n\nBad:\n\n```typescript\nconst myPkg = require('my-pkg');\n\nmodule.exports = {\n plugins: [\n [\n 'babel-plugin-transform-rewrite-imports',\n {\n replaceExtensions: {\n '^packages/([^/]+)(/.+)?': ({ specifier, capturingGroups }) => {\n myPkg.doStuff(specifier, capturingGroups);\n }\n }\n }\n ]\n ]\n};\n```\n\nTechnically, you can get away with violating this rule if you're _sure_ you'll\nonly ever use [dynamic imports/require statements with string literal\narguments][32].\n\n## Comprehensive Logging\n\nLike Babel itself, this plugin leverages [debug (via rejoinder)][33] under the\nhood for log management. You can take advantage of this to peer into\ntransform-rewrite-imports's innermost workings and deepest decision-making\nprocesses by [activating][34] the appropriate log level. For example, the\nfollowing will enable all logging related to this plugin:\n\n```bash\nDEBUG='babel-plugin-transform-rewrite-imports:*' npx babel src --out-dir dist\n```\n\n## Examples\n\nWith the following snippet integrated into your Babel configuration:\n\n```typescript\nconst {\n defaultRecognizedExtensions\n} = require('babel-plugin-transform-rewrite-imports');\n\nmodule.exports = {\n plugins: [\n [\n 'babel-plugin-transform-rewrite-imports',\n {\n appendExtension: '.mjs',\n recognizedExtensions: [...defaultRecognizedExtensions, '.css'],\n replaceExtensions: {\n '.ts': '.mjs',\n '^package$': `${__dirname}/package.json`,\n '(.+?)\\\\.less$': '$1.css'\n }\n }\n ]\n ]\n};\n```\n\nThe following source:\n\n```typescript\n/* file: src/index.ts */\nimport { name as pkgName } from 'package';\nimport { primary } from '.';\nimport { secondary } from '..';\nimport { tertiary } from '../..';\nimport dirImport from './some-dir/';\nimport jsConfig from './jsconfig.json';\nimport projectConfig from './project.config.cjs';\nimport { add, double } from './src/numbers';\nimport { curry } from './src/typed/curry.ts';\nimport styles from './src/less/styles.less';\n\n// Note that, unless otherwise configured, @babel/preset-typescript deletes\n// type-only imports. If you want to operate on type imports and/or .d.ts files,\n// use @babel/syntax-typescript instead. See ./test/supports-type-only for\n// an example.\nimport type * as AllTypes from './lib/something.mjs';\n\nexport { triple, quadruple } from './lib/num-utils';\n\n// Note that, unless otherwise configured, @babel/preset-typescript deletes\n// type-only exports. If you want to operate on type imports and/or .d.ts files,\n// use @babel/syntax-typescript instead. See ./test/supports-type-only for\n// an example.\nexport type { NamedType } from './lib/something';\n\nconst thing = await import('./thing');\nconst anotherThing = require('./another-thing');\n\nconst thing2 = await import(someFn(`./${someVariable}`) + '.json');\nconst anotherThing2 = require(someOtherVariable);\n```\n\nIs, depending on your other plugins/settings, transformed into something like:\n\n```typescript\n/* file: dist/index.js */\nconst _rewrite = (importPath, options) => {\n ...\n },\n _rewrite_options = {\n appendExtension: '.mjs',\n recognizedExtensions: ['.js', '.jsx', '.mjs', '.cjs', '.json', '.css'],\n replaceExtensions: {\n '.ts': '.mjs',\n '^package$': '/absolute/path/to/project/package.json',\n '(.+?)\\\\.less$': '$1.css'\n }\n };\n\nimport { name as pkgName } from '/absolute/path/to/project/package.json';\nimport { primary } from './index.mjs';\nimport { secondary } from '../index.mjs';\nimport { tertiary } from '../../index.mjs';\nimport dirImport from './some-dir/index.mjs';\nimport jsConfig from './jsconfig.json';\nimport projectConfig from './project.config.cjs';\nimport { add, double } from './src/numbers.mjs';\nimport { curry } from './src/typed/curry.mjs';\nimport styles from './src/less/styles.css';\n\nexport { triple, quadruple } from './lib/num-utils.mjs';\n\nconst thing = await import('./thing.mjs');\nconst anotherThing = require('./another-thing.mjs');\n\n// Require calls and dynamic imports with a non-string-literal first argument\n// are transformed into function calls that dynamically return the rewritten\n// string:\n\nconst thing2 = await import(\n _rewrite(someFn(`./${someVariable}`) + '.json', _rewrite_options)\n);\n\nconst anotherThing2 = require(_rewrite(someOtherVariable, _rewrite_options));\n\n```\n\n> [!NOTE]\n>\n> See the full output of this example [here][35].\n\n### Real-World Examples\n\nFor some real-world examples of this Babel plugin in action, check out\n[symbiote's `babel.config.js` file][19] (which uses transform-rewrite-imports to\nreplace both babel-plugin-module-resolver and tsconfig-replace-paths),\n[unified-utils][36], [this very repository][37], or just take a peek at the\n[test cases][38].\n\n\n\n## Appendix\n\n\n\nFurther documentation can be found under [`docs/`][x-repo-docs].\n\n\n\n### Published Package Details\n\nThis is a [CJS2 package][x-pkg-cjs-mojito] with statically-analyzable exports\nbuilt by Babel for use in Node.js versions that are not end-of-life. For\nTypeScript users, this package supports both `\"Node10\"` and `\"Node16\"` module\nresolution strategies.\n\n\n\n\nExpand details\n\nThat means both CJS2 (via `require(...)`) and ESM (via `import { ... } from ...`\nor `await import(...)`) source will load this package from the same entry points\nwhen using Node. This has several benefits, the foremost being: less code\nshipped/smaller package size, avoiding [dual package\nhazard][x-pkg-dual-package-hazard] entirely, distributables are not\npacked/bundled/uglified, a drastically less complex build process, and CJS\nconsumers aren't shafted.\n\nEach entry point (i.e. `ENTRY`) in [`package.json`'s\n`exports[ENTRY]`][x-repo-package-json] object includes one or more [export\nconditions][x-pkg-exports-conditions]. These entries may or may not include: an\n[`exports[ENTRY].types`][x-pkg-exports-types-key] condition pointing to a type\ndeclaration file for TypeScript and IDEs, a\n[`exports[ENTRY].module`][x-pkg-exports-module-key] condition pointing to\n(usually ESM) source for Webpack/Rollup, a `exports[ENTRY].node` and/or\n`exports[ENTRY].default` condition pointing to (usually CJS2) source for Node.js\n`require`/`import` and for browsers and other environments, and [other\nconditions][x-pkg-exports-conditions] not enumerated here. Check the\n[package.json][x-repo-package-json] file to see which export conditions are\nsupported.\n\nNote that, regardless of the [`{ \"type\": \"...\" }`][x-pkg-type] specified in\n[`package.json`][x-repo-package-json], any JavaScript files written in ESM\nsyntax (including distributables) will always have the `.mjs` extension. Note\nalso that [`package.json`][x-repo-package-json] may include the\n[`sideEffects`][x-pkg-side-effects-key] key, which is almost always `false` for\noptimal [tree shaking][x-pkg-tree-shaking] where appropriate.\n\n\n\n\n\n\n### License\n\n\n\nSee [LICENSE][x-repo-license].\n\n\n\n## Contributing and Support\n\n**[New issues][x-repo-choose-new-issue] and [pull requests][x-repo-pr-compare]\nare always welcome and greatly appreciated! 🤩** Just as well, you can [star 🌟\nthis project][x-badge-repo-link] to let me know you found it useful! ✊🏿 Or [buy\nme a beer][x-repo-sponsor], I'd appreciate it. Thank you!\n\nSee [CONTRIBUTING.md][x-repo-contributing] and [SUPPORT.md][x-repo-support] for\nmore information.\n\n\n\n\n### Contributors\n\n\n\n\n\n\n[](#contributors-)\n\n\n\n\nThanks goes to these wonderful people ([emoji\nkey][x-repo-all-contributors-emojis]):\n\n\n\n\n\n\n
![](\"https://raw.githubusercontent.com/Xunnamius/babel-plugin-transform-rewrite-imports/refs/heads/main/logo.png\"){kind=logo}
\n![\"Bernard\"/](\"https://avatars.githubusercontent.com/u/656017?v=4?s=100\")
![](\"https://raw.githubusercontent.com/all-contributors/all-contributors-cli/1b8533af435da9854653492b1327a23a4dbd0a10/assets/logo-small.svg\"){kind=logo}
\n Add your contributions\n \n