aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Jarred Sumner <jarred@jarredsumner.com> 2021-09-23 23:28:45 -0700
committerGravatar Jarred Sumner <jarred@jarredsumner.com> 2021-09-23 23:28:45 -0700
commit10c01af692bd1cc4d761c2fddea110e777283390 (patch)
tree1de6d40520c2ad56ec3c38cdbd0448f3876d2163
parenta68a1983cf3ca2b50f40a56843f101fab140e48b (diff)
downloadbun-10c01af692bd1cc4d761c2fddea110e777283390.tar.gz
bun-10c01af692bd1cc4d761c2fddea110e777283390.tar.zst
bun-10c01af692bd1cc4d761c2fddea110e777283390.zip
Update README.md
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 860ed110a..74ab0bacb 100644
--- a/README.md
+++ b/README.md
@@ -422,7 +422,7 @@ Run `bun bun ./path-to.js` to generate a `node_modules.bun` file containing all
- For browsers, loading entire apps without bundling dependencies is typically slow. With a fast bundler & transpiler, the bottleneck eventually becomes the web browser's ability to run many network requests concurrently. There are many workarounds for this. `<link rel="modulepreload">`, HTTP/3, etc but none are more effective than bundling. If you have reproducible evidence to the contrary, feel free to submit an issue. It would be better if bundling wasn't necessary.
- On the server, bundling reduces the number of filesystem lookups to load JavaScript. While filesystem lookups are faster than HTTP requests, there's still overhead.
-**What is .bun?**
+**What is `.bun`?**
The `.bun` file contains: