# Bun bun-v0.0.22 — Release & Upgrade Intelligence
- **Product:** Bun (https://bun.sh)
- **Version:** bun-v0.0.22
- **Released:** Sep 25, 2021
- **Impact Score:** 5/10
- **Breaking Changes:** Not verified
- **Canonical Analysis:** https://changelogs.us/bun/updates/bun-v0.0.22/

## Executive Summary (TL;DR)
Bun bun-v0.0.22. Source highlight: Support resolving `"exports"` field in package.json. Webpack's guide does a great job explaining the `"exports"` field.

## New Features
- Support resolving `"exports"` field in package.json. Webpack's guide does a great job explaining the `"exports"` field.
- Add parsed lines of code counter to `bun bun`
- Support importing files above the project root. HTTP Requests above the project root are allowlisted to specific file extensions to prevent common webserver security vulnerabilities like reading `/etc/passwd`. Absolute file path imports always start with `abs:`. The security questions aren't as relevant for localhost development, but still worth thinking about.
- Support bundling symlinked workspace packages via `bun bun`. To use this, set `"bun": { "alwaysBundle": ["packageName"] }` in the project's `package.json`.
- When bundling JSON, print the output as `JSON.parse(jsonString)` when the JSON is ASCII. `JSON.parse` is much faster for JavaScript engines to parse.
- Add comment explaining failed package.json parsing optimization

## Bug Fixes
- Fix handling when file metadata store exceeds statically allocated count (at time of writing, 16k)
- Always log errors when generating `node_modules.server.bun`
- Fix how error lines with strings are highlighted
- Fix parsing/printing JavaScript unicode identifiers
- Slightly improve .env loader string detection
- More correct `export default` transform for bundled code
