Skip to content

Commit 431ccf9

Browse files
bakuzanianschmitz
authored andcommitted
Clarify production build output files documentation (#6786)
1 parent e59e092 commit 431ccf9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docusaurus/docs/production-build.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -5,15 +5,15 @@ title: Creating a Production Build
55

66
`npm run build` creates a `build` directory with a production build of your app. Inside the `build/static` directory will be your JavaScript and CSS files. Each filename inside of `build/static` will contain a unique hash of the file contents. This hash in the file name enables [long term caching techniques](#static-file-caching).
77

8-
When running a production build of freshly created Create React App application, there are 3 `.js` files (called _chunks_) that are generated and placed in the `build/static/js` directory:
8+
When running a production build of freshly created Create React App application, there are a number of `.js` files (called _chunks_) that are generated and placed in the `build/static/js` directory:
99

1010
`main.[hash].chunk.js`
1111

1212
- This is your _application_ code. `App.js`, etc.
1313

14-
`1.[hash].chunk.js`
14+
`[number].[hash].chunk.js`
1515

16-
- This is your _vendor_ code, which includes modules you've imported from within `node_modules`. One of the potential advantages with splitting your _vendor_ and _application_ code is to enable [long term caching techniques](#static-file-caching) to improve application loading performance. Since _vendor_ code tends to change less often than the actual _application_ code, the browser will be able to cache them separately, and won't re-download them each time the app code changes.
16+
- These files can either be _vendor_ code, or [code splitting chunks](code-splitting.md). _Vendor_ code includes modules that you've imported from within `node_modules`. One of the potential advantages with splitting your _vendor_ and _application_ code is to enable [long term caching techniques](#static-file-caching) to improve application loading performance. Since _vendor_ code tends to change less often than the actual _application_ code, the browser will be able to cache them separately, and won't re-download them each time the app code changes.
1717

1818
`runtime~main.[hash].js`
1919

0 commit comments

Comments
 (0)