Skip to content

Commit 0b17ab3

Browse files
authored
fix: broken links in docs/guide/why.md (#17800)
1 parent 84e6d60 commit 0b17ab3

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/guide/why.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Vite improves the dev server start time by first dividing the modules in an appl
1818

1919
- **Dependencies** are mostly plain JavaScript that do not change often during development. Some large dependencies (e.g. component libraries with hundreds of modules) are also quite expensive to process. Dependencies may also be shipped in various module formats (e.g. ESM or CommonJS).
2020

21-
Vite [pre-bundles dependencies](./dep-pre-bundling) using [esbuild](https://esbuild.github.io/). esbuild is written in Go and pre-bundles dependencies 10-100x faster than JavaScript-based bundlers.
21+
Vite [pre-bundles dependencies](./dep-pre-bundling.md) using [esbuild](https://esbuild.github.io/). esbuild is written in Go and pre-bundles dependencies 10-100x faster than JavaScript-based bundlers.
2222

2323
- **Source code** often contains non-plain JavaScript that needs transforming (e.g. JSX, CSS or Vue/Svelte components), and will be edited very often. Also, not all source code needs to be loaded at the same time (e.g. with route-based code-splitting).
2424

@@ -47,7 +47,7 @@ Once you experience how fast Vite is, we highly doubt you'd be willing to put up
4747

4848
Even though native ESM is now widely supported, shipping unbundled ESM in production is still inefficient (even with HTTP/2) due to the additional network round trips caused by nested imports. To get the optimal loading performance in production, it is still better to bundle your code with tree-shaking, lazy-loading and common chunk splitting (for better caching).
4949

50-
Ensuring optimal output and behavioral consistency between the dev server and the production build isn't easy. This is why Vite ships with a pre-configured [build command](./build) that bakes in many [performance optimizations](./features#build-optimizations) out of the box.
50+
Ensuring optimal output and behavioral consistency between the dev server and the production build isn't easy. This is why Vite ships with a pre-configured [build command](./build.md) that bakes in many [performance optimizations](./features.md#build-optimizations) out of the box.
5151

5252
## Why Not Bundle with esbuild?
5353

@@ -59,4 +59,4 @@ Rollup has also been working on performance improvements, [switching its parser
5959

6060
## How is Vite Different from X?
6161

62-
You can check out the [Comparisons](./comparisons) section for more details on how Vite differs from other similar tools.
62+
You can check out the [Comparisons](./comparisons.md) section for more details on how Vite differs from other similar tools.

0 commit comments

Comments
 (0)