From dea0d6cd11d95ab4f0d747d7513d02115daf8a52 Mon Sep 17 00:00:00 2001 From: Patrik Oldsberg Date: Fri, 11 Oct 2024 12:00:17 +0200 Subject: [PATCH] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Fredrik Adelöw Signed-off-by: Patrik Oldsberg --- docs/tooling/cli/02-build-system.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tooling/cli/02-build-system.md b/docs/tooling/cli/02-build-system.md index 96c46bed6a..f1fb5f6c9e 100644 --- a/docs/tooling/cli/02-build-system.md +++ b/docs/tooling/cli/02-build-system.md @@ -365,7 +365,7 @@ load performance. ### Backend Development The backend development setup does not use any bundling process. It runs a -Node.js process directly, with only-the-fly transpilation from TypeScript to +Node.js process directly, with on-the-fly transpilation from TypeScript to JavaScript. The transpilation is done with a custom transform based on [SWC](https://swc.rs/). @@ -375,7 +375,7 @@ order to store data between restarts, the backend process has an IPC channel available to store and restore data from the parent CLI process. The primary purpose of this, which is already built-in, is to restore the contents of databases when using SQLite for development. You can also use it for your own -purposes too, with the `DevDataStore` utility exported from the +purposes, with the `DevDataStore` utility exported from the `@backstage/backend-dev-utils` package. If you want to inspect the running Node.js process, the `--inspect` and