aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Jarred Sumner <jarred@jarredsumner.com> 2022-04-08 06:32:29 -0700
committerGravatar Jarred Sumner <jarred@jarredsumner.com> 2022-04-08 06:32:29 -0700
commitd5173f71d4b213b2279ccb7c7ba04a0220db6917 (patch)
tree5c2c42628c340fe35ae7aabac71491fb13fc867e
parent61ca99cfd997b8b9e548ca530b5442d06aa0a2c5 (diff)
downloadbun-d5173f71d4b213b2279ccb7c7ba04a0220db6917.tar.gz
bun-d5173f71d4b213b2279ccb7c7ba04a0220db6917.tar.zst
bun-d5173f71d4b213b2279ccb7c7ba04a0220db6917.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 6c8d52f84..c5c2993b0 100644
--- a/README.md
+++ b/README.md
@@ -408,7 +408,7 @@ bun's bundler & transpiler are great for building websites &amp; webapps, but no
Today, bun is mostly focused on compatibility with existing frameworks & tooling.
-Ideally, most projects can use bun with their existing tooling while making few changes to their codebase. That means using bun in development, and continuing to use Webpack, esbuild, or another bundler in production. Using two bundlers might sound strange at first, but after all the production-only AST transforms, minification, and special development/production-only imported files...it’s not far from the status quo.
+Ideally, most projects can use bun with their existing tooling while making few changes to their codebase. For frontend work, that means using bun in development, and continuing to use Webpack, esbuild, or another bundler in production. Using two bundlers might sound strange at first, but after all the production-only AST transforms, minification, and special development/production-only imported files...it’s not far from the status quo.
Longer-term, bun intends to replace Node.js, Webpack, Babel, and PostCSS (in production).