Skip to content

Commit d79728f

Browse files
docs: initial content for Choosing an editor (#18)
Co-authored-by: Nathan Walker <[email protected]>
1 parent 332162f commit d79728f

File tree

2 files changed

+48
-0
lines changed

2 files changed

+48
-0
lines changed

content/guide/choosing-an-editor.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: Choosing An Editor
3+
---
4+
5+
You can develop NativeScript apps in any text editor or IDE you prefer.
6+
7+
### VS Code
8+
9+
Most of the NativeScript team prefers to use [VS Code from Microsoft](https://code.visualstudio.com/) as their editor for NativeScript apps. Some reasons we use VS Code:
10+
11+
- Visual Studio Code has excellent support for [TypeScript](https://www.typescriptlang.org/).
12+
- Visual Studio Code gives you the ability to debug JavaScript and TypeScript code directly in your editor. The NativeScript team maintains an official [NativeScript Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=NativeScript.nativescript) that enables step debugging for NativeScript apps.
13+
- Visual Studio Code is a fast, modern editor that Microsoft [updates frequently](https://code.visualstudio.com/updates/).
14+
- Visual Studio Code is available for Windows, macOS, and Linux.
15+
- Microsoft backs Visual Studio Code; therefore, you can feel confident that the editor will continue to be supported in the future.
16+
17+
If you do choose to [try Visual Studio Code](https://code.visualstudio.com/), let's look at one tip you might find useful as you develop NativeScript apps.
18+
19+
- The `code` command
20+
21+
After you install Visual Studio Code, you can open projects using the editor's `File``Open` menu option, but there's an alternative option that works far better for command-line-based projects like NativeScript: the `code` command.
22+
23+
The `code` command runs in your command-line or terminal, and it works just like the `ns` command does for NativeScript apps. Visual Studio Code installs the `code` command by default on Windows on Linux, but on macOS, there's [one manual step](https://code.visualstudio.com/docs/setup/mac) you must perform.
24+
25+
Once set up, you can type `code .` in your terminal to open the files in your current folder for editing. For example, you could use the following sequence of command to create a new NativeScript app and open it for editing.
26+
27+
```cli
28+
ns create MyNewApp
29+
cd MyNewApp
30+
code .
31+
```
32+
33+
### WebStorm
34+
35+
If you're a WebStorm user, check out this [popular community-written plugin](https://plugins.jetbrains.com/webstorm/plugin/8588-nativescript) that adds many NativeScript-related features.
36+
37+
### Next steps
38+
39+
<!-- TODO: fix links -->
40+
41+
- [NativeScripting](https://nativescripting.com/)
42+
- The third-party NativeScripting site has many video courses to teach you everything you need to know about NativeScript, including a collection of free courses to help you get started.
43+
- [Code Samples](https://nativescript.org/samples/)
44+
- The NativeScript team provides a collection of high-quality code samples you can add to your applications. Perusing the code samples is a great way to get familiar with what NativeScript can do, as well as find the code you can use on your next app.

content/sidebar.ts

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,10 @@ export default [
2626
text: 'Using Modals',
2727
link: '/guide/navigation/modals',
2828
},
29+
{
30+
text: 'Choosing an editor',
31+
link: '/guide/choosing-an-editor'
32+
},
2933
{
3034
text: 'Troubleshooting',
3135
link: '/troubleshooting',

0 commit comments

Comments
 (0)