ImportMeta

interface ImportMeta

• readonly dir: string

  Absolute path to the directory containing the source file, without a trailing slash

• dirname: string

  Alias of import.meta.dir. Exists for Node.js compatibility

• readonly env: Env & ProcessEnv & ImportMetaEnv

  The environment variables of the process

  import.meta.env === process.env

• readonly file: string

  Filename of the source file

• filename: string

  Alias of import.meta.path. Exists for Node.js compatibility

• hot: { data: any; accept(): void; dispose(cb: (data: any) => void | Promise<void>): void; off(event: HMREvent, callback: () => void): void; on(event: HMREvent, callback: () => void): void }

  Hot module replacement (HMR) APIs. In production this value is undefined, so you can guard HMR code with an if statement:

  if (import.meta.hot) {
    // HMR APIs are available
  }

  The check is usually unnecessary: Bun dead-code-eliminates calls to the HMR APIs in production builds.

  https://bun.com/docs/bundler/hmr

• main: boolean

  true if the current file started the process

  if (import.meta.main) {
   console.log("I started the process!");
  }

• readonly path: string

  Absolute path to the source file

• require: Require

  Load a CommonJS module within an ES Module. Bun's transpiler rewrites all calls to require with import.meta.require when transpiling ES Modules for the runtime.

  Warning: This API is not stable and may change or be removed in the future. Use at your own risk.

• url: string

  file:// url string for the current module.

  console.log(import.meta.url);
  "file:///Users/me/projects/my-app/src/my-app.ts"

• resolve(

  specifier: string

  ): string;

  resolve(

  specifier: string,

  parent?: string | URL

  ): string;

  import.meta.resolve is a module-relative resolution function scoped to each module, returning the URL string.

  const dependencyAsset = import.meta.resolve('component-lib/asset.css');
  // file:///app/node_modules/component-lib/asset.css
  import.meta.resolve('./dep.js');
  // file:///app/dep.js

  All features of the Node.js module resolution are supported. Dependency resolutions are subject to the permitted exports resolutions within the package.

  Caveats:

  • This can result in synchronous file-system operations, which can impact performance similarly to require.resolve.
  • This feature is not available within custom loaders (it would create a deadlock).

  @param specifier

  The module specifier to resolve relative to the current module.

  @param parent

  An optional absolute parent module URL to resolve from. Default: import.meta.url

  @returns

  The absolute URL string that the specifier would resolve to.