\n\n## Install\n\n```sh\nnpm install --save-dev @esbuild-kit/esm-loader\n```\n\n## Usage\n\nPass `@esbuild-kit/esm-loader` into the [`--loader`](https://nodejs.org/api/cli.html#--experimental-loadermodule) flag.\n```sh\nnode --loader @esbuild-kit/esm-loader ./file.ts\n```\n\n### TypeScript configuration\nThe following properties are used from `tsconfig.json` in the working directory:\n- [`strict`](https://www.typescriptlang.org/tsconfig#strict): Whether to transform to strict mode\n- [`jsx`](https://esbuild.github.io/api/#jsx): Whether to transform JSX\n\t> **Warning:** When set to `preserve`, the JSX syntax will remain untransformed. To prevent Node.js from throwing a syntax error, chain another Node.js loader that can transform JSX to JS.\n- [`jsxFactory`](https://esbuild.github.io/api/#jsx-factory): How to transform JSX\n- [`jsxFragmentFactory`](https://esbuild.github.io/api/#jsx-fragment): How to transform JSX Fragments\n- [`jsxImportSource`](https://www.typescriptlang.org/tsconfig#jsxImportSource): Where to import JSX functions from\n- [`allowJs`](https://www.typescriptlang.org/tsconfig#allowJs): Whether to apply the tsconfig to JS files\n- [`paths`](https://www.typescriptlang.org/tsconfig#paths): For resolving aliases\n\n#### Custom `tsconfig.json` path\nBy default, `tsconfig.json` will be detected from the current working directory.\n\nTo set a custom path, use the `ESBK_TSCONFIG_PATH` environment variable:\n\n```sh\nESBK_TSCONFIG_PATH=./path/to/tsconfig.custom.json node --loader @esbuild-kit/esm-loader ./file.ts\n```\n\n### Cache\nModules transformations are cached in the system cache directory ([`TMPDIR`](https://en.wikipedia.org/wiki/TMPDIR)). Transforms are cached by content hash so duplicate dependencies are not re-transformed.\n\nSet environment variable `ESBK_DISABLE_CACHE` to a truthy value to disable the cache:\n\n```sh\nESBK_DISABLE_CACHE=1 node --loader @esbuild-kit/esm-loader ./file.ts\n```\n\n \n\n
\n\n## FAQ\n\n### Can it import JSON modules?\nYes. This loader transpiles JSON modules so it's also compatible with named imports.\n\n### Can it import ESM modules over network?\n\nNode.js has built-in support for network imports [behind the `--experimental-network-imports` flag](https://nodejs.org/api/esm.html#network-based-loading-is-not-enabled-by-default).\n\nYou can pass it in with `esm-loader`:\n\n```sh\nnode --loader @esbuild-kit/esm-loader --experimental-network-imports ./file.ts\n```\n\n### Can it resolve files without an extension?\n\nIn ESM, import paths must be explicit (must include file name and extension).\n\nFor backwards compatibility, this loader adds support for classic Node resolution for extensions: `.js`, `.json`, `.ts`, `.tsx`, `.jsx`. Resolving a `index` file by the directory name works too.\n\n```js\nimport file from './file' // -> ./file.js\nimport directory from './directory' // -> ./directory/index.js\n```\n\n### Can it use Node.js's CommonJS resolution algorithm?\n\nESM import resolution expects explicit import paths, whereas CommonJS resolution expects implicit imports (eg. extensionless & directory imports).\n\nAs a result of this change, Node.js changes how it imports a path that matches both a file and directory. In ESM, the directory would be imported, but in CJS, the file would be imported.\n\nTo use to the CommonJS resolution algorithm, use the [`--experimental-specifier-resolution=node`](https://nodejs.org/api/cli.html#--experimental-specifier-resolutionmode) flag.\n\n```sh\nnode --loader @esbuild-kit/esm-loader --experimental-specifier-resolution=node ./file.ts\n```\n\n## Related\n\n- [tsx](https://github.com/esbuild-kit/tsx) - Node.js runtime powered by esbuild using [`@esbuild-kit/cjs-loader`](https://github.com/esbuild-kit/cjs-loader) and [`@esbuild-kit/esm-loader`](https://github.com/esbuild-kit/esm-loader).\n\n- [@esbuild-kit/cjs-loader](https://github.com/esbuild-kit/cjs-loader) - TypeScript & ESM to CJS transpiler using the Node.js loader API.\n\n## Sponsors\n\n
![](\"https://cdn.jsdelivr.net/gh/privatenumber/sponsors/sponsorkit/sponsors.svg\")
\n\t\n