Bun File Types

File Types

File types and loaders supported by Bun's bundler and runtime

The Bun bundler implements a set of default loaders out of the box. As a rule of thumb, the bundler and the runtime both support the same set of file types out of the box.

.js .cjs .mjs .mts .cts .ts .tsx .jsx .css .json .jsonc .json5 .toml .yaml .yml .txt .wasm .node .html .sh

Bun uses the file extension to determine which built-in loader should be used to parse the file. Every loader has a name, such as js, tsx, or json. These names are used when building plugins that extend Bun with custom loaders.

You can explicitly specify which loader to use using the 'type' import attribute.

import my_toml from "./my_file" with { type: "toml" };
// or with dynamic imports
const { default: my_toml } = await import("./my_file", { with: { type: "toml" } });

Built-in loaders

js

JavaScript. Default for .cjs and .mjs.

Parses the code and applies a set of default transforms like dead-code elimination and tree shaking. Note that Bun does not attempt to down-convert syntax at the moment.

jsx

JavaScript + JSX.. Default for .js and .jsx.

Same as the js loader, but JSX syntax is supported. By default, JSX is down-converted to plain JavaScript; the details of how this is done depends on the jsx* compiler options in your tsconfig.json. Refer to the TypeScript documentation on JSX for more information.

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

TypeScript + JSX loader. Default for .tsx. Transpiles both TypeScript and JSX to vanilla JavaScript.

json

JSON loader. Default for .json.

JSON files can be directly imported.

import pkg from "./package.json";
pkg.name; // => "my-package"

During bundling, the parsed JSON is inlined into the bundle as a JavaScript object.

var pkg = {
  name: "my-package",
  // ... other fields
};
pkg.name;

If a .json file is passed as an entrypoint to the bundler, it will be converted to a .js module that export defaults the parsed object.

export default {
  name: "John Doe",
  age: 35,
  email: "johndoe@example.com",
};

jsonc

JSON with Comments loader. Default for .jsonc.

JSONC (JSON with Comments) files can be directly imported. Bun will parse them, stripping out comments and trailing commas.

import config from "./config.jsonc";
console.log(config);

During bundling, the parsed JSONC is inlined into the bundle as a JavaScript object, identical to the json loader.

var config = {
  option: "value",
};

toml

TOML loader. Default for .toml.

TOML files can be directly imported. Bun will parse them with its fast native TOML parser.

import config from "./bunfig.toml";
config.logLevel; // => "debug"

// via import attribute:
// import myCustomTOML from './my.config' with {type: "toml"};

During bundling, the parsed TOML is inlined into the bundle as a JavaScript object.

var config = {
  logLevel: "debug",
  // ...other fields
};
config.logLevel;

If a .toml file is passed as an entrypoint, it will be converted to a .js module that export defaults the parsed object.

export default {
  name: "John Doe",
  age: 35,
  email: "johndoe@example.com",
};

yaml

YAML loader. Default for .yaml and .yml.

YAML files can be directly imported. Bun will parse them with its fast native YAML parser.

import config from "./config.yaml";
console.log(config);

// via import attribute:
import data from "./data.txt" with { type: "yaml" };

During bundling, the parsed YAML is inlined into the bundle as a JavaScript object.

var config = {
  name: "my-app",
  version: "1.0.0",
  // ...other fields
};

If a .yaml or .yml file is passed as an entrypoint, it will be converted to a .js module that export defaults the parsed object.

export default {
  name: "John Doe",
  age: 35,
  email: "johndoe@example.com",
};

json5

JSON5 loader. Default for .json5.

JSON5 files can be directly imported. Bun will parse them with its fast native JSON5 parser. JSON5 is a superset of JSON that supports comments, trailing commas, unquoted keys, single-quoted strings, and more.

import config from "./config.json5";
console.log(config);

// via import attribute:
import data from "./data.txt" with { type: "json5" };

During bundling, the parsed JSON5 is inlined into the bundle as a JavaScript object.

var config = {
  name: "my-app",
  version: "1.0.0",
  // ...other fields
};

If a .json5 file is passed as an entrypoint, it will be converted to a .js module that export defaults the parsed object.

export default {
  name: "John Doe",
  age: 35,
  email: "johndoe@example.com",
};

text

Text loader. Default for .txt.

The contents of the text file are read and inlined into the bundle as a string. Text files can be directly imported. The file is read and returned as a string.

import contents from "./file.txt";
console.log(contents); // => "Hello, world!"

// To import an html file as text
// The "type' attribute can be used to override the default loader.
import html from "./index.html" with { type: "text" };

When referenced during a build, the contents are inlined into the bundle as a string.

var contents = `Hello, world!`;
console.log(contents);

If a .txt file is passed as an entrypoint, it will be converted to a .js module that export defaults the file contents.

export default "Hello, world!";

napi

Native addon loader. Default for .node.

In the runtime, native addons can be directly imported.

import addon from "./addon.node";
console.log(addon);

In the bundler, .node files are handled using the file loader.

sqlite

SQLite loader. with { "type": "sqlite" } import attribute

In the runtime and bundler, SQLite databases can be directly imported. This will load the database using bun:sqlite.

import db from "./my.db" with { type: "sqlite" };

This is only supported when the target is bun.

By default, the database is external to the bundle (so that you can potentially use a database loaded elsewhere), so the database file on-disk won't be bundled into the final output.

You can change this behavior with the "embed" attribute:

// embed the database into the bundle
import db from "./my.db" with { type: "sqlite", embed: "true" };

When using a standalone executable, the database is embedded into the single-file executable.

Otherwise, the database to embed is copied into the outdir with a hashed filename.

html

The html loader processes HTML files and bundles any referenced assets. It will:

• Bundle and hash referenced JavaScript files (<script src="...">)
• Bundle and hash referenced CSS files (<link rel="stylesheet" href="...">)
• Hash referenced images (<img src="...">)
• Preserve external URLs (by default, anything starting with http:// or https://)

For example, given this HTML file:

It will output a new HTML file with the bundled assets:

Under the hood, it uses lol-html to extract script and link tags as entrypoints, and other assets as external.

Currently, the list of selectors is:

• audio[src]
• iframe[src]
• img[src]
• img[srcset]
• link:not([rel~='stylesheet']):not([rel~='modulepreload']):not([rel~='manifest']):not([rel~='icon']):not([rel~='apple-touch-icon'])[href]
• link[as='font'][href], link[type^='font/'][href]
• link[as='image'][href]
• link[as='style'][href]
• link[as='video'][href], link[as='audio'][href]
• link[as='worker'][href]
• link[rel='icon'][href], link[rel='apple-touch-icon'][href]
• link[rel='manifest'][href]
• link[rel='stylesheet'][href]
• script[src]
• source[src]
• source[srcset]
• video[poster]
• video[src]

The html loader behaves differently depending on how it's used:

1. Static Build: When you run bun build ./index.html, Bun produces a static site with all assets bundled and hashed.

2. Runtime: When you run bun run server.ts (where server.ts imports an HTML file), Bun bundles assets on-the-fly during development, enabling features like hot module replacement.

3. Full-stack Build: When you run bun build --target=bun server.ts (where server.ts imports an HTML file), the import resolves to a manifest object that Bun.serve uses to efficiently serve pre-bundled assets in production.

css

CSS loader. Default for .css.

CSS files can be directly imported. This is primarily useful for full-stack applications where CSS is bundled alongside HTML.

import "./styles.css";

There isn't any value returned from the import, it's only used for side effects.

sh loader

Bun Shell loader. Default for .sh files

This loader is used to parse Bun Shell scripts. It's only supported when starting Bun itself, so it's not available in the bundler or in the runtime.

bun run ./script.sh

file

File loader. Default for all unrecognized file types.

The file loader resolves the import as a path/URL to the imported file. It's commonly used for referencing media or font assets.

import logo from "./logo.svg";
console.log(logo);

In the runtime, Bun checks that the logo.svg file exists and converts it to an absolute path to the location of logo.svg on disk.

bun run logo.ts
/path/to/project/logo.svg

In the bundler, things are slightly different. The file is copied into outdir as-is, and the import is resolved as a relative path pointing to the copied file.

var logo = "./logo.svg";
console.log(logo);

If a value is specified for publicPath, the import will use value as a prefix to construct an absolute path/URL.

This loader is copied into the outdir as-is. The name of the copied file is determined using the value of naming.asset.

// TypeScript error
// Cannot find module './logo.svg' or its corresponding type declarations.

This can be fixed by creating *.d.ts file anywhere in your project (any name will work) with the following contents:

declare module "*.svg" {
  const content: string;
  export default content;
}

This tells TypeScript that any default imports from .svg should be treated as a string.