Open integrated terminal on visual studio code ( View Integrated Terminal) type 'node filename.js' press enter. The Visual Studio Code editor has built-in debugging support for the Node.js runtime and can debug JavaScript, TypeScript, and many other languages that are transpiled into JavaScript. Setting up a project for Node.js debugging is straightforward with VS Code providing appropriate launch configuration defaults and snippets. How to develop and debug Node.js with Visual Studio Code Prepare your environment. Install Visual Studio Code. Visual Studio Code integrates with git to provide. Clone sample project to local computer. Open Visual Studio Code. Press F1 to display the command palette. Right-click the npm node to take one of the following actions. Install New npm Packages Opens the UI to install new packages.; Install npm Packages Runs the npm install command to install all packages listed in package.json. (Runs npm install.); Update npm Packages Updates packages to the latest versions, according to the semantic versioning (SemVer) range specified in package.json.
In this guide you will learn how to:
Dockerfile
file for an Express Node.js service containerCreate a folder for the project.
Open a development command prompt in the project folder and create the project:
Open the project folder in VS Code.
Open the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)) and use Docker: Add Docker Files to Workspace... command:
Select Node.js when prompted for the application platform.
Select either Yes or No when prompted to include Docker Compose files. Compose is typically used when running multiple containers at once.
Enter 3000
when prompted for the application port.
The extension creates Dockerfile
and .dockerignore
files. If you elected to include Docker Compose files, docker-compose.yml
and docker-compose.debug.yml
will be generated as well. Finally, the extension will create a set of VS Code tasks in .vscode/tasks.json
for building and running the container (in both debug- and release-configurations) and a launch debug configuration in .vscode/launch.json
for debugging the service within the container.
The Docker extension helps you author Dockerfiles by using IntelliSense to provide auto-completions and contextual help. To see this feature in action, add an environment variable to your service image by following these steps:
Open the Dockerfile
file.
Use ENV
instruction to add an environment variable to the service container image.
Note how the Docker extension lists all available Dockerfile instructions and describes the syntax.
The Docker extension uses the
base
stage of theDockerfile
to create a debug version of the container image for your service. Put the environment variable definition in thebase
stage to have this variable available in both debug and release versions of the container image.
Save the Dockerfile
file.
Open a terminal (⌃` (Windows, Linux Ctrl+`)).
Enter npm run start
to start the application:
Open the web browser and navigate to http://localhost:3000. You should see a page similar to the following:
When done testing, type Ctrl+C in the terminal.
Open the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)) and select the Docker Images: Build Image... command.
Open the Docker Explorer and verify that the new image is visible in the Images tree:
Right-click on the image built in the previous section and select Run or Run Interactive. The container should start and you should be able to see it in the Docker Containers tree:
Open the web browser and navigate to http://localhost:3000. You should see a page similar to the following:
When done testing, right-click the container in the Containers tree and select Stop.
When the Docker extension adds files to the application, it also adds a VS Code debugger configuration in .vscode/launch.json
for debugging the service when running inside a container. The extension detects the protocol and port used by the service and points the browser to the service.
Set a breakpoint in the get()
handler for the '/'
route in routes/index.js
.
Make sure the Docker Node.js Launch debugger configuration is selected.
Start debugging (use the F5 key).
index.js
.Note that, because the debugger attaches after the application starts, the breakpoint may missed the first time around; you might have to refresh the browser to see the debugger break on the second try.
You can configure the application to wait for the debugger to attach before starting execution by setting the inspectMode property to
break
in thedocker-run: debug
task intasks.json
under thenode
object.
You can view the logs in VS Code by using the View Logs command on the container:
Navigate to the Docker Explorer.
In the Containers tab, right-click on your container and choose View Logs.
The output will be displayed in the terminal.
You're done! Now that your container is ready, you may want to:
Vue.js is a popular JavaScript library for building web application user interfaces and Visual Studio Code has built-in support for the Vue.js building blocks of HTML, CSS, and JavaScript. For a richer Vue.js development environment, you can install the Vetur extension which supports Vue.js IntelliSense, code snippets, formatting, and more.
We'll be using the Vue CLI for this tutorial. If you are new to the Vue.js framework, you can find great documentation and tutorials on the vuejs.org website.
To install and use the Vue CLI as well as run the Vue application server, you'll need the Node.js JavaScript runtime and npm (the Node.js package manager) installed. npm is included with Node.js which you can install from Node.js downloads.
Tip: To test that you have Node.js and npm correctly installed on your machine, you can type node --version
and npm --version
.
To install the vue/cli
, in a terminal or command prompt type:
This may take a few minutes to install. You can now create a new Vue.js application by typing:
where my-app
is the name of the folder for your application. You will be prompted to select a preset and you can keep the default (babel, eslint)
, which will use Babel to transpile the JavaScript to browser compatible ES5 and install the ESLint linter to detect coding errors. It may take a few minutes to create the Vue application and install its dependencies.
Let's quickly run our Vue application by navigating to the new folder and typing npm run serve
to start the web server and open the application in a browser:
You should see 'Welcome to your Vue.js App' on http://localhost:8080 in your browser. You can press Ctrl+C to stop the vue-cli-service
server.
To open your Vue application in VS Code, from a terminal (or command prompt), navigate to the my-app
folder and type code .
:
VS Code will launch and display your Vue application in the File Explorer.
Now expand the src
folder and select the App.vue
file. You'll notice that VS Code doesn't show any syntax highlighting and it treats the file as Plain Text as you can see in the lower right Status Bar. You'll also see a notification recommending the Vetur extension for the .vue
file type.
The Vetur extension supplies Vue.js language features (syntax highlighting, IntelliSense, snippets, formatting) to VS Code.
From the notification, press Install to download and install the Vetur extension. You should see the Vetur extension Installing in the Extensions view. Once the installation is complete (may take several minutes), the Install button will change to the Manage gear button.
Now you should see that .vue
is a recognized file type for the Vue language and you have language features such as syntax highlighting, bracket matching, and hover descriptions.
As you start typing in App.vue
, you'll see smart suggestions or completions both for HTML and CSS but also for Vue.js specific items like declarations (v-bind
, v-for
) in the Vue template
section:
and Vue properties (methods
, computed
) in the scripts
section:
VS Code through the Vue extension language service can also provide type definition information in the editor through Go to Definition (F12) or Peek Definition (⌥F12 (Windows Alt+F12, Linux Ctrl+Shift+F10)). Put the cursor over the App
, right click and select Peek Definition. A Peek window will open showing the App
definition from App.js
.
Press Escape to close the Peek window.
Let's update the sample application to 'Hello World!'. In App.vue
replace the HelloWorld component msg
custom attribute text with 'Hello World!'.
Once you save the App.vue
file (⌘S (Windows, Linux Ctrl+S)), restart the server with npm run serve
and you'll see 'Hello World!'. Leave the server running while we go on to learn about Vue.js client side debugging.
Tip: VS Code supports Auto Save, which by default saves your files after a delay. Check the Auto Save option in the File menu to turn on Auto Save or directly configure the files.autoSave
user setting.
Linters analyze your source code and can warn you about potential problems before you run your application. The Vue ESLint plugin (eslint-plugin-vue) checks for Vue.js specific syntax errors which are shown in the editor as red squigglies and are also displayed in the Problems panel (View > Problems⇧⌘M (Windows, Linux Ctrl+Shift+M)).
Below you can see an error when the Vue linter detects more than one root element in a template:
You can debug client side Vue.js code with the Debugger for Chrome extension. You can learn more from the Vue.js debugging in Chrome and VS Code recipe on the VS Code debugging recipes site.
Note: There are currently issues with the sourcemaps generated by vue-cli, which cause issues with the debugging experience in VS Code. See https://github.com/vuejs/vue-loader/issues/1163.
Another popular tool for debugging Vue.js is the vue-devtools plug-in.
Vetur is only one of many Vue.js extensions available for VS Code. You can search in the Extensions view (⇧⌘X (Windows, Linux Ctrl+Shift+X)) by typing 'vue'.
There are also Extension Packs which bundle extensions that other people have found useful for Vue.js development.