From 696b79e3470bd2adc618453d6ce272aa4ade8d6e Mon Sep 17 00:00:00 2001 From: Matt Kantor Date: Fri, 8 Sep 2023 01:15:40 -0700 Subject: [PATCH] docs(vite-node): fix typos in vite-node README (#4082) --- packages/vite-node/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/vite-node/README.md b/packages/vite-node/README.md index 7674ffc1cd9a..2f199d2269b0 100644 --- a/packages/vite-node/README.md +++ b/packages/vite-node/README.md @@ -130,7 +130,7 @@ await server.close() Sometimes you might want to inspect the transformed code to investigate issues. You can set environment variable `VITE_NODE_DEBUG_DUMP=true` to let vite-node write the transformed result of each module under `.vite-node/dump`. -If you want to debug by modifying the dumped code, you can change the value of `VITE_NODE_DEBUG_DUMP` to `load` and search for the dumpped files and use them for executing. +If you want to debug by modifying the dumped code, you can change the value of `VITE_NODE_DEBUG_DUMP` to `load` and search for the dumped files and use them for executing. ```bash VITE_NODE_DEBUG_DUMP=load vite-node example.ts @@ -151,7 +151,7 @@ const server = new ViteNodeServer(viteServer, { ### Debug Execution -If the process get stuck, it might because there is a unresolvable circular dependencies, you can set `VITE_NODE_DEBUG_RUNNER=true` to vite-node warn about it. +If the process gets stuck, it might be because there are unresolvable circular dependencies. You can set `VITE_NODE_DEBUG_RUNNER=true` for vite-node to warn about this. ```bash VITE_NODE_DEBUG_RUNNER=true vite-node example.ts