Commit 46c99ed
doc: fix duplicate word "for for" in compile cache
PR-URL: #62917
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Jacob Smith <jacob@frende.me>
Reviewed-By: Daeyeon Jeong <daeyeon.dev@gmail.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>1 parent 6e097ee commit 46c99ed
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -406,7 +406,7 @@ This may slow down the first load of a module graph, but subsequent loads of the | |||
| 406 | 406 | graph may get a significant speedup if the contents of the modules do not change. | |
| 407 | 407 | ||
| 408 | 408 | To clean up the generated compile cache on disk, simply remove the cache directory. The cache | |
| 409 | - directory will be recreated the next time the same directory is used for for compile cache | ||
| 409 | + directory will be recreated the next time the same directory is used for compile cache | ||
| 410 | 410 | storage. To avoid filling up the disk with stale cache, it is recommended to use a directory | |
| 411 | 411 | under the [`os.tmpdir()`][]. If the compile cache is enabled by a call to | |
| 412 | 412 | [`module.enableCompileCache()`][] without specifying the `directory`, Node.js will use | |
0 commit comments