# Loaders (/bundler/loaders)
Related: [Fullstack dev server](/bundler/fullstack.md), [Hot reloading](/bundler/hot-reloading.md), [HTML & static sites](/bundler/html-static.md), [Standalone HTML](/bundler/standalone-html.md), [CSS](/bundler/css.md), [Single-file executable](/bundler/executables.md)
The Bun bundler has a set of built-in loaders.
> As a rule of thumb: **the bundler and the runtime both support the same set of file types by default.**
`.js` `.cjs` `.mjs` `.mts` `.cts` `.ts` `.tsx` `.jsx` `.css` `.json` `.jsonc` `.json5` `.toml` `.yaml` `.yml` `.xml` `.txt` `.text` `.md` `.markdown` `.wasm` `.node` `.html` `.sh`
Bun uses the file extension to choose which built-in loader parses the file. Every loader has a name, such as `js`, `tsx`, or `json`. Plugins that extend Bun with custom loaders refer to these names.
To specify a loader explicitly, use the `'type'` import attribute.
```ts title="index.ts" icon="/icons/typescript.svg"
import my_toml from "./my_file" with { type: "toml" };
// or with dynamic imports
const { default: my_toml } = await import("./my_file", { with: { type: "toml" } });
```
With TypeScript 7.1 or newer, `@types/bun` types these imports from the `type` attribute: a `type: "text"` import is a
`string`, a `type: "sqlite"` import is a `Database`. Older TypeScript versions type the import from the file extension
alone.
## Built-in loaders [#built-in-loaders]
### `js` [#js]
**JavaScript loader.** Default for `.cjs` and `.mjs`.
Parses the code and applies a set of default transforms like dead-code elimination and tree shaking. Bun does not down-convert syntax.
***
### `jsx` [#jsx]
**JavaScript + JSX loader.** Default for `.js` and `.jsx`.
Same as the `js` loader, but JSX syntax is supported. By default, Bun down-converts JSX to plain JavaScript. The exact output depends on the `jsx*` compiler options in your `tsconfig.json`. See the [TypeScript documentation on JSX](https://www.typescriptlang.org/tsconfig#jsx).
***
### `ts` [#ts]
**TypeScript loader.** Default for `.ts`, `.mts`, and `.cts`.
Strips out all TypeScript syntax, then behaves identically to the `js` loader. Bun does not perform typechecking.
***
### `tsx` [#tsx]
**TypeScript + JSX loader.** Default for `.tsx`.
Transpiles both TypeScript and JSX to vanilla JavaScript.
***
### `json` [#json]
**JSON loader.** Default for `.json`.
JSON files can be directly imported.
```js
import pkg from "./package.json";
pkg.name; // => "my-package"
```
During bundling, Bun inlines the parsed JSON into the bundle as a JavaScript object.
```js
const pkg = {
name: "my-package",
// ... other fields
};
pkg.name;
```
If you pass a `.json` file as an entrypoint to the bundler, Bun converts it to a `.js` module that `export default`s the parsed object.
Input
Output
```json
{
"name": "John Doe",
"age": 35,
"email": "johndoe@example.com"
}
```
```js
export default {
name: "John Doe",
age: 35,
email: "johndoe@example.com",
};
```
***
### `jsonc` [#jsonc]
**JSON with Comments loader.** Default for `.jsonc`.
JSONC (JSON with Comments) files can be directly imported. Bun parses them, stripping out comments and trailing commas.
```js
import config from "./config.jsonc";
console.log(config);
```
During bundling, Bun inlines the parsed JSONC into the bundle as a JavaScript object, identical to the `json` loader.
```js
var config = {
option: "value",
};
```
Bun automatically uses the `jsonc` loader for `tsconfig.json`, `jsconfig.json`, `package.json`, and `bun.lock` files.
***
### `toml` [#toml]
**TOML loader.** Default for `.toml`.
TOML files can be directly imported. Bun parses them with its native TOML parser.
```js
import config from "./bunfig.toml";
config.logLevel; // => "debug"
// with an import attribute:
// import myCustomTOML from './my.config' with {type: "toml"};
```
During bundling, Bun inlines the parsed TOML into the bundle as a JavaScript object.
```js
var config = {
logLevel: "debug",
// ...other fields
};
config.logLevel;
```
If you pass a `.toml` file as an entrypoint, Bun converts it to a `.js` module that `export default`s the parsed object.
Input
Output
```toml
name = "John Doe"
age = 35
email = "johndoe@example.com"
```
```js
export default {
name: "John Doe",
age: 35,
email: "johndoe@example.com",
};
```
***
### `yaml` [#yaml]
**YAML loader.** Default for `.yaml` and `.yml`.
YAML files can be directly imported. Bun parses them with its native YAML parser.
```js
import config from "./config.yaml";
console.log(config);
// with an import attribute:
import data from "./data.txt" with { type: "yaml" };
```
During bundling, Bun inlines the parsed YAML into the bundle as a JavaScript object.
```js
var config = {
name: "my-app",
version: "1.0.0",
// ...other fields
};
```
If you pass a `.yaml` or `.yml` file as an entrypoint, Bun converts it to a `.js` module that `export default`s the parsed object.
Input
Output
```yaml
name: John Doe
age: 35
email: johndoe@example.com
```
```js
export default {
name: "John Doe",
age: 35,
email: "johndoe@example.com",
};
```
***
### `xml` [#xml]
**XML loader.** Default for `.xml`.
XML files can be directly imported. Bun parses them with its native XML 1.0 parser into the compact object shape of [`Bun.XML.parse`](/runtime/xml):
* One key for the root element
* `"@name"` keys for attributes
* Arrays for repeated child elements
* `"#text"` for text next to attributes or children
* Every value is a string
```ts
import doc from "./config.xml";
console.log(doc.config["@version"]);
// via import attribute:
import feed from "./export.rss" with { type: "xml" };
```
During bundling, Bun inlines the parsed XML into the bundle as a JavaScript object.
```ts
var doc = {
config: {
"@version": "2",
// ...other fields
},
};
```
If you pass a `.xml` file as an entrypoint, Bun converts it to a `.js` module that `export default`s the parsed object.
Input
Output
```xml
John Doe
johndoe@example.com
admin
editor
```
```ts
export default {
user: {
"@id": "1",
name: "John Doe",
email: "johndoe@example.com",
role: ["admin", "editor"],
},
};
```
***
### `text` [#text]
**Text loader.** Default for `.txt` and `.text`.
Text files can be directly imported. Bun reads the file and returns it as a string.
```js
import contents from "./file.txt";
console.log(contents); // => "Hello, world!"
// To import an html file as text
// The "type" attribute overrides the default loader.
import html from "./index.html" with { type: "text" };
```
When the file is referenced during a build, Bun inlines the contents into the bundle as a string.
```js
var contents = `Hello, world!`;
console.log(contents);
```
If you pass a `.txt` file as an entrypoint, Bun converts it to a `.js` module that `export default`s the file contents.
Input
Output
```txt
Hello, world!
```
```js
export default "Hello, world!";
```
***
### `napi` [#napi]
**Native addon loader.** Default for `.node`.
In the runtime, native addons can be directly imported.
```js
import addon from "./addon.node";
console.log(addon);
```
In the bundler, Bun handles
`.node`
files with the
`file`
loader.
***
### `sqlite` [#sqlite]
**SQLite loader.** Requires `with { "type": "sqlite" }` import attribute.
In the runtime and bundler, SQLite databases can be directly imported. Bun loads the database with `bun:sqlite`.
```js
import db from "./my.db" with { type: "sqlite" };
```
The
`sqlite`
loader is only supported when the target is
`bun`
.
By default, Bun does not bundle the database file on disk into the final output. The database file stays external to the bundle, so you can use a database loaded elsewhere.
You can change this behavior with the `"embed"` attribute:
```js
// embed the database into the bundle
import db from "./my.db" with { type: "sqlite", embed: "true" };
```
With a standalone executable, Bun embeds the database into the single-file executable.
Otherwise, the database to embed is copied into the `outdir` with a hashed filename.
***
### `html` [#html]
**HTML loader.** Default for `.html`.
The `html` loader processes HTML files and bundles any referenced assets. It:
* Bundles and hashes referenced JavaScript files (`