aboutsummaryrefslogtreecommitdiff
path: root/docs/bundler/macros.md
diff options
context:
space:
mode:
authorGravatar 0xflotus <0xflotus@gmail.com> 2023-07-29 12:58:45 +0200
committerGravatar GitHub <noreply@github.com> 2023-07-29 03:58:45 -0700
commitdccf82b1c682a84c42540ba9e00e5e9296cc7e5f (patch)
tree18778b43288415fb057049992c7d2d914bbc31ee /docs/bundler/macros.md
parent5563be99d33d02f2e7ddc1c3fadcb0cffeee72d8 (diff)
downloadbun-dccf82b1c682a84c42540ba9e00e5e9296cc7e5f.tar.gz
bun-dccf82b1c682a84c42540ba9e00e5e9296cc7e5f.tar.zst
bun-dccf82b1c682a84c42540ba9e00e5e9296cc7e5f.zip
docs: fixed small errors (#3879)
* Update cache.md * Update index.md * Update macros.md * Update writing.md
Diffstat (limited to '')
-rw-r--r--docs/bundler/macros.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/bundler/macros.md b/docs/bundler/macros.md
index 729f8350b..ecba16c0d 100644
--- a/docs/bundler/macros.md
+++ b/docs/bundler/macros.md
@@ -33,7 +33,7 @@ As you can see, the source code of the `random` function occurs nowhere in the b
## When to use macros
-If you have several build scripts for small things where you would otherwise have a one-off build script, bundle-time code execution can be easier to maintain. It lives with the rest of your code, it runs with the rest of the build, it is automatically paralellized, and if it fails, the build fails too.
+If you have several build scripts for small things where you would otherwise have a one-off build script, bundle-time code execution can be easier to maintain. It lives with the rest of your code, it runs with the rest of the build, it is automatically parallelized, and if it fails, the build fails too.
If you find yourself running a lot of code at bundle-time though, consider running a server instead.