Impact Score: 5/10
Bun v0.0.41
Source available โ automated, not human-reviewed
Component: bun ยท Channel: stable. Automated analysis, not a compatibility certification. How this works.
Analysis updated: 2026-11-01.
โก Executive Summary (TL;DR)
Bun bun-v0.0.41. Source highlight: `bun run ./file.js` now supports running JavaScript, TS, TSX, and JSX files using Bun.js. If you pass `bun run` a filepath to a `.js`, `.jsx`, `.tsx`, or `.ts` file, it will run it with Bun.js instead of saying `"error: Missing script"`. This is very experimental!
Who Does This Impact? (Role-Based Analysis)
๐ป Software Engineers & Devs
Check the source notes against the package and APIs you use before upgrading.
๐ Product & Engineering Leads
Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.
โ๏ธ DevOps & Security
Verify the target version, runtime requirements and rollback procedure in the official documentation.
โก Performance & Enhancements (1)
- `performance.now()` is implemented
๐ง Bug Fixes & Patches (2)
- [.env loader] functions from bash were exported incorrectly due to parsing process environment variables similarly to `.env` files which is unnecessary. Now process environment variables are passed through without extra parsing
- `fetch()` wasn't working due to a silly mistake. That's fixed
๐ View Raw Release Notes (Original Developer Log)
To upgrade:
```bash
bun upgrade
```
### What's new:
`bun run`:
`bun run ./file.js` now supports running JavaScript, TS, TSX, and JSX files using Bun.js. If you pass `bun run` a filepath to a `.js`, `.jsx`, `.tsx`, or `.ts` file, it will run it with Bun.js instead of saying `"error: Missing script"`. This is very experimental!
#### Bun.js
<sup>Bun.js is Bun's JavaScript runtime environment. </sup>
- Top-level await works now
- `performance.now()` is implemented
### Bug fixes
- [.env loader] functions from bash were exported incorrectly due to parsing process environment variables similarly to `.env` files which is unnecessary. Now process environment variables are passed through without extra parsing
- `fetch()` wasn't working due to a silly mistake. That's fixed