Skip to content

Commit

Permalink
Fix legacy "Built-in Debugger" link in Korean
Browse files Browse the repository at this point in the history
Update built-in debugger link to the latest in [guides/debugging-getting-started](https://nodejs.org/en/docs/guides/debugging-getting-started/).
  • Loading branch information
ZYSzys authored and fhemberger committed Dec 19, 2018
1 parent 39a7f4e commit d001e32
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions locale/ko/docs/guides/debugging-getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -313,7 +313,7 @@ TCP 포트(기본 `5858`)로 지금은 중단된 V8 디버깅 프로토콜에서
V8 디버깅 프로토콜은 더는 관리되지 않고 문서화도 되지 않습니다.

<!--
#### [Built-in Debugger](https://github.com/nodejs/node/blob/master/lib/_debugger.js)
#### [Built-in Debugger](https://nodejs.org/dist/latest-v6.x/docs/api/debugger.html)
Start `node debug script_name.js` to start your script under Node's builtin
command-line debugger. Your script starts in another Node process started with
Expand All @@ -327,7 +327,7 @@ which translates the Inspector Protocol used in Chromium to the V8 Debugger
protocol used in Node.js.
-->

#### [내장 디버거](https://github.com/nodejs/node/blob/master/lib/_debugger.js)
#### [내장 디버거](https://nodejs.org/dist/latest-v6.x/docs/api/debugger.html)

Node의 내장 명령형 디버거로 스크립트를 실행하려면 `node debug script_name.js`로 실행하세요.
스크립트가 다른 Node 프로세스에서 `--debug-brk` 옵션으로 시작되고 원래의 Node 프로세스는
Expand Down

0 comments on commit d001e32

Please sign in to comment.