From b62af73b229e300f9ee15dbfbc84d3aa1b032dc8 Mon Sep 17 00:00:00 2001 From: Evan You Date: Tue, 19 May 2020 14:48:40 -0400 Subject: [PATCH] chore: update comments --- src/node/server/serverPluginHmr.ts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/node/server/serverPluginHmr.ts b/src/node/server/serverPluginHmr.ts index 2b9841cda4a117..a8e588b432adf2 100644 --- a/src/node/server/serverPluginHmr.ts +++ b/src/node/server/serverPluginHmr.ts @@ -12,13 +12,13 @@ // that it accepts hot updates (by importing from the `/vite/hmr` special module) // 5. If any parent chain exhausts without ever running into an HMR boundary, // it's considered a "dead end". This causes a full page reload. -// 6. If a `.vue` boundary is encountered, we add it to the `vueImports` Set. +// 6. If a `.vue` boundary is encountered, we add it to the `vueBoundaries` Set. // 7. If a `.js` boundary is encountered, we check if the boundary's current // child importer is in the accepted list of the boundary (see additional // explanation below). If yes, record current child importer in the -// `jsImporters` Set. +// `jsBoundaries` Set. // 8. If the graph walk finished without running into dead ends, send the -// client to update all `jsImporters` and `vueImporters`. +// client to update all `jsBoundaries` and `vueBoundaries`. // How do we get a js HMR boundary's accepted list on the server // 1. During the import rewriting, if `/vite/hmr` import is present in a js file,