@@ -37,7 +37,7 @@ See the output of the tool for command-line options and next steps.
3737### Running a program from npm
3838
3939The ` nodejs_binary ` rule lets you run a program with Node.js.
40- See [ Built-ins]
40+ See [ Built-ins] ( Built-ins.html )
4141
4242If you have installed the [ rollup] package, you could write this rule:
4343
@@ -126,7 +126,7 @@ See https://nodejs.org/en/docs/guides/debugging-getting-started/ for more detail
126126
127127### Debugging with VS Code
128128
129- With the above configuration you can use VS Code as your debugger.
129+ With the above configuration you can use VS Code as your debugger.
130130You will first need to configure your ` .vscode/launch.json ` :
131131
132132```
@@ -143,13 +143,13 @@ You will first need to configure your `.vscode/launch.json`:
143143 "../../../../../*": "${workspaceRoot}/*",
144144 // do as many levels here as needed for your project
145145 }
146- ```
147- We use ` sourceMapPathOverrides ` here to rewrite the source maps produced by ` ts_library ` so that breakpoints line up with the source maps.
146+ ```
147+ We use ` sourceMapPathOverrides ` here to rewrite the source maps produced by ` ts_library ` so that breakpoints line up with the source maps.
148148Once configured start your process with
149149```
150150bazel run --config=debug //test:test1
151151```
152- Then hit ` F5 ` which will start the VS Code debugger with the ` Attach nodejs_binary ` configuration.
152+ Then hit ` F5 ` which will start the VS Code debugger with the ` Attach nodejs_binary ` configuration.
153153VS Code will immediatenly hit a breakpoint to which you can continue and debug using all the normal debug features provided.
154154
155155
@@ -168,7 +168,7 @@ To stamp a build, you must pass the `--stamp` argument to Bazel.
168168Also pass the ` workspace_status_command ` argument to ` bazel build ` .
169169We prefer to do these with an entry in ` .bazelrc ` :
170170
171- ``` sh
171+ ``` sh
172172# This tells Bazel how to interact with the version control system
173173# Enable this with --config=release
174174build:release --stamp --workspace_status_command=./tools/bazel_stamp_vars.sh
0 commit comments