You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/start/cli-basics.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -258,10 +258,10 @@ You now know how to create and run NativeScript apps. Your next step is learning
258
258
There are two main paths you can take when you want to debug a NativeScript application:
259
259
260
260
-**Chrome**
261
-
The default way of debugging a NativeScript application is by using the integration with Chrome. You can find more information on the actual steps [here](http://docs.nativescript.org/tooling/debugging).
261
+
The default way of debugging a NativeScript application is by using the integration with Chrome. You can find more information on the actual steps [here](https://docs.nativescript.org/tooling/debugging/chrome-devtools).
262
262
263
263
-**Visual Studio Code**
264
-
One of the preferred ways of debugging a NativeScript application is with the [NativeScript extension for Visual Studio Code](http://docs.nativescript.org/tooling/debugging#debugging-with-visual-studio-code).
264
+
One of the preferred ways of debugging a NativeScript application is with the [NativeScript extension for Visual Studio Code](https://docs.nativescript.org/tooling/visual-studio-code-extension).
265
265
266
266
You’ll want to check out the Chrome Dev Tools and the Visual Studio debugger as you need to step through your JavaScript code or TypeScript code, but for the moment let’s look at how to do some simple logging in your apps.
0 commit comments