Out of scope rfcs/out-of-scope/rfc-bun-path-url.md

Bun.fileURLToPath / Bun.pathToFileURL — file URL ↔ path

Moved backlog → out-of-scope. Identical surface to node:url with no

Out-of-scope (2026-05-31)

Moved backlog → out-of-scope. Identical surface to node:url with no Bun-specific advantage — there is nothing for patties to own. If a future spec ever needs a file:// ↔ path round-trip, it inlines node:url at that one call site. Permanent no.

Summary

Convert between file:// URLs and OS paths. Mirrors node:url functions.

Why backlog

Framework uses string paths from Bun.Glob and config-relative resolution. No code path round-trips file URLs today.

This entry is borderline out-of-scope: identical surface to Node, no value-add beyond convenience.

Trigger to promote to draft

  • Plugin loader needs to resolve relative imports from a plugin file's import.meta.url, OR
  • Edge adapter starts dealing with file URLs from a different runtime.

Bun-unique classification

Standard — identical to node:url. No Bun-specific advantage; if we ever need this, importing from node:url is fine.

Open questions when promoted

  • Honestly: do we ever ship this, or just import { fileURLToPath } from "node:url" at the use site?