Debugging Chrome in VS Code

ΠŸΠΎΠ΄Π΅Π»ΠΈΡ‚ΡŒΡΡ
HTML-ΠΊΠΎΠ΄
  • ΠžΠΏΡƒΠ±Π»ΠΈΠΊΠΎΠ²Π°Π½ΠΎ: 24 Π°ΠΏΡ€ 2018
  • Note: This does not use the "Chrome remote debugger protocol". This uses the 'chrome.debugger' API. Here is the documentation that explains the difference. developer.chrome.com/docs/ext...
    Thanks @Tarek Faham for point that out in the comments πŸ‘‡
  • КиноКино

ΠšΠΎΠΌΠΌΠ΅Π½Ρ‚Π°Ρ€ΠΈΠΈ • 9

  • @workingTchr
    @workingTchr 2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄

    When they said "you can get all this started with an npm script", that's when I bailed.

  • @TarekFaham
    @TarekFaham 2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄

    This is not chrome remote debugging.

    • @_heyMP
      @_heyMP  2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄

      How so?

    • @TarekFaham
      @TarekFaham 2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄

      @@_heyMP remote debugging you have to attach vscode to a running instance of chrome with remote debugging enabled. What you explained is launching chrome from vscode not attaching.

    • @_heyMP
      @_heyMP  2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄

      ​@@TarekFaham Interesting. "The chrome.debugger API serves as an alternate transport for Chrome's remote debugging protocol." Good to know. VSCode still attaches to a Chrome process but it does it via a new API. Good to know!

    • @TarekFaham
      @TarekFaham 2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄

      @@_heyMP I provided my feedback after landing on your video several times while researching how to debug javascript web application running on a remote sever not locally. This is the difference.

    • @_heyMP
      @_heyMP  2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄

      @@TarekFaham Fair point. I'll update the title to make it less ambiguous. πŸ‘