Phpstorm Nodejs

Phpstorm Node Js Docker
Phpstorm Nodejs Debug

Setting up PHPStorm to work with Laravel. Laravel is a wonderful framework that has a wide range of features and many implementations that make life easier for a programmer. However, the downside to this convenience is the difficulty in reading the code for the IDE. Node.js is a lightweight runtime environment for executing JavaScript outside the browser, for example on the server or in the command line. PhpStorm integrates with Node.js providing assistance in configuring, editing, running, debugging, testing, profiling, and maintaining your applications. Windows node.js less phpstorm. Improve this question. Follow edited Apr 2 '13 at 2:42. 123k 26 26 gold badges 200 200 silver badges 246 246 bronze. The issue was fixed for that user in WebStorm 7.0.1 Perhaps this issue will be fixed in a point release of phpStorm if the fixes are merged into the codebase. Finally, I'm aware that the mention of the browser in the phpStorm web help is a red herring, perhaps the documentation should be updated to accommodate the running/debugging of NodeJS.

-->

If you are using Node.js professionally, find performance speed and system call compatibility important, want to run Docker containers that leverage Linux workspaces and avoid having to maintain both Linux and Windows build scripts, or just prefer using a Bash command line, then you want to install Node.js on the Windows Subsystem for Linux (more specifically, WSL 2).

Using Windows Subsystem for Linux (WSL), enables you to install your preferred Linux distribution (Ubuntu is our default) so that you can have consistency between your development environment (where you write code) and production environment (the server where your code is deployed).

Note

If you are new to developing with Node.js and want to get up and running quickly so that you can learn, install Node.js on Windows. This recommendation also applies if you plan to use a Windows Server production environment.

Phpstorm Node Js Docker

Install WSL 2

WSL 2 is the most recent version available on Windows 10 and we recommend it for professional Node.js development workflows. To enable and install WSL 2, follow the steps in the WSL install documentation. These steps will include choosing a Linux distribution (for example, Ubuntu).

Once you have installed WSL 2 and a Linux distribution, open the Linux distribution (it can be found in your Windows start menu) and check the version and codename using the command: lsb_release -dc.

We recommend updating your Linux distribution regularly, including immediately after you install, to ensure you have the most recent packages. Windows doesn't automatically handle this update. To update your distribution, use the command: sudo apt update && sudo apt upgrade.

Install Windows Terminal (optional)

Windows Terminal is an improved command line shell that allows you to run multiple tabs so that you can quickly switch between Linux command lines, Windows Command Prompt, PowerShell, Azure CLI, or whatever you prefer to use. You can also create custom key bindings (shortcut keys for opening or closing tabs, copy+paste, etc.), use the search feature, customize your terminal with themes (color schemes, font styles and sizes, background image/blur/transparency), and more. Learn more in the Windows Terminal docs.

Install Windows Terminal using the Microsoft Store: By installing via the store, updates are handled automatically.

Install nvm, node.js, and npm

Besides choosing whether to install on Windows or WSL, there are additional choices to make when installing Node.js. We recommend using a version manager as versions change very quickly. You will likely need to switch between multiple versions of Node.js based on the needs of different projects you're working on. Node Version Manager, more commonly called nvm, is the most popular way to install multiple versions of Node.js. We will walk through the steps to install nvm and then use it to install Node.js and Node Package Manager (npm). There are alternative version managers to consider as well covered in the next section.

Important

It is always recommended to remove any existing installations of Node.js or npm from your operating system before installing a version manager as the different types of installation can lead to strange and confusing conflicts. For example, the version of Node that can be installed with Ubuntu's apt-get command is currently outdated. For help with removing previous installations, see How to remove nodejs from ubuntu.)

Open your Ubuntu 18.04 command line.
Install cURL (a tool used for downloading content from the internet in the command-line) with: sudo apt-get install curl
Install nvm, with: curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash
Note
At the time of publication, NVM v0.35.3 was the most recent version available. You can check the GitHub project page for the latest release of NVM, and adjust the above command to include the newest version.Installing the newer version of NVM using cURL will replace the older one, leaving the version of Node you've used NVM to install intact. For example: curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.36.0/install.sh | bash
To verify installation, enter: command -v nvm ...this should return 'nvm', if you receive 'command not found' or no response at all, close your current terminal, reopen it, and try again. Learn more in the nvm github repo.
List which versions of Node are currently installed (should be none at this point): nvm ls
Install the current release of Node.js (for testing the newest feature improvements, but more likely to have issues): nvm install node
Install the latest stable LTS release of Node.js (recommended): nvm install --lts
List what versions of Node are installed: nvm ls ...now you should see the two versions that you just installed listed.
Verify that Node.js is installed and the currently default version with: node --version. Then verify that you have npm as well, with: npm --version (You can also use which node or which npm to see the path used for the default versions).
To change the version of Node.js you would like to use for a project, create a new project directory mkdir NodeTest, and enter the directory cd NodeTest, then enter nvm use node to switch to the Current version, or nvm use --lts to switch to the LTS version. You can also use the specific number for any additional versions you've installed, like nvm use v8.2.1. (To list all of the versions of Node.js available, use the command: nvm ls-remote).

If you are using NVM to install Node.js and NPM, you should not need to use the SUDO command to install new packages.

Alternative version managers

While nvm is currently the most popular version manager for node, there are a few alternatives to consider:

n is a long-standing nvm alternative that accomplishes the same thing with slightly different commands and is installed via npm rather than a bash script.
fnm is a newer version manager, claiming to be much faster than nvm. (It also uses Azure Pipelines.)
Volta is a new version manager from the LinkedIn team that claims improved speed and cross-platform support.
asdf-vm is a single CLI for multiple languages, like ike gvm, nvm, rbenv & pyenv (and more) all in one.
nvs (Node Version Switcher) is a cross-platform nvm alternative with the ability to integrate with VS Code.

Install Visual Studio Code

We recommend using Visual Studio Code with the Remote-development extension pack for Node.js projects. This splits VS Code into a “client-server” architecture, with the client (the VS Code user interface) running on your Windows operating system and the server (your code, Git, plugins, etc) running 'remotely' on your WSL Linux distribution.

Note

This “remote” scenario is a bit different than you may be accustomed to. WSL supports an actual Linux distribution where your project code is running, separately from your Windows operating system, but still on your local machine. The Remote-WSL extension connects with your Linux subsystem as if it were a remote server, though it’s not running in the cloud… it’s still running on your local machine in the WSL environment that you enabled to run alongside Windows.

Linux-based Intellisense and linting is supported.
Your project will automatically build in Linux.
You can use all your extensions running on Linux (ES Lint, NPM Intellisense, ES6 snippets, etc.).

Other code editors, like IntelliJ, Sublime Text, Brackets, etc. will also work with a WSL 2 Node.js development environment, but may not have the same sort of remote features that VS Code offers. These code editors may run into trouble accessing the WSL shared network location (wsl$Ubuntuhome) and will try to build your Linux files using Windows tools, which likely not what you want. The Remote-WSL Extension in VS Code handles this compatibility for you, with other IDEs you may need to set up an X server. Support for running GUI apps in WSL (like a code editor IDE) is coming soon.

Terminal-based text editors (vim, emacs, nano) are also helpful for making quick changes from right inside your console. The article, Emacs, Nano, or Vim: Choose your Terminal-Based Text Editor Wisely does a nice job explaining some differences and a bit about how to use each.

To install VS Code and the Remote-WSL Extension:

Download and install VS Code for Windows. VS Code is also available for Linux, but Windows Subsystem for Linux does not support GUI apps, so we need to install it on Windows. Not to worry, you'll still be able to integrate with your Linux command line and tools using the Remote - WSL Extension.
Install the Remote - WSL Extension on VS Code. This allows you to use WSL as your integrated development environment and will handle compatibility and pathing for you. Learn more.

Important

Phpstorm Nodejs Debug

If you already have VS Code installed, you need to ensure that you have the 1.35 May release or later in order to install the Remote - WSL Extension. We do not recommend using WSL in VS Code without the Remote-WSL extension as you will lose support for auto-complete, debugging, linting, etc. Fun fact: This WSL extension is installed in $HOME/.vscode-server/extensions.

Helpful VS Code Extensions

While VS Code comes with many features for Node.js development out of the box, there are some helpful extensions to consider installing available in the Node.js Extension Pack. Install them all or pick and choose which seem the most useful to you.

To install the Node.js extension pack:

Open the Extensions window (Ctrl+Shift+X) in VS Code.
The Extensions window is now divided into three sections (because you installed the Remote-WSL extension).
- 'Local - Installed': The extensions installed for use with your Windows operating system.
- 'WSL:Ubuntu-18.04-Installed': The extensions installed for use with your Ubuntu operating system (WSL).
- 'Recommended': Extensions recommended by VS Code based on the file types in your current project.
In the search box at the top of the Extensions window, enter: Node Extension Pack (or the name of whatever extension you are looking for). The extension will be installed for either your Local or WSL instances of VS Code depending on where you have the current project opened. You can tell by selecting the remote link in the bottom-left corner of your VS Code window (in green). It will either give you the option to open or close a remote connection. Install your Node.js extensions in the 'WSL:Ubuntu-18.04' environment.

A few additional extensions you may want to consider include:

Debugger for Chrome: Once you finish developing on the server side with Node.js, you'll need to develop and test the client side. This extension integrates your VS Code editor with your Chrome browser debugging service, making things a bit more efficient.
Keymaps from other editors: These extensions can help your environment feel right at home if you're transitioning from another text editor (like Atom, Sublime, Vim, eMacs, Notepad++, etc).
Settings Sync: Enables you to synchronize your VS Code settings across different installations using GitHub. If you work on different machines, this helps keep your environment consistent across them.

Set up Git (optional)

To set up Git for a NodeJS project on WSL, see the article Get started using Git on Windows Subsystem for Linux in the WSL documentation.

Skip to end of metadataGo to start of metadata

This tutorial describes how to run and debug Node.js applications in WebStorm.
Go to this tutorial for getting started with Node.js in WebStorm.

Running Node.js app locally

To run your Node.js application locally on your machine, you need to create a new Node.js Run/Debug configuration.

Click Edit configurations in the top right-hand corner of the IDE window or in the main menu Run.

Сlick + to add a new configuration and seleсt Node.js type.

Specify the path to the JavaScript file that needs to be executed. You can also add any parameters you need to pass to the node (Node parameters input) or to your application (Application parameters input) on the start.

Select this new configuration from the drop-down list on the top-right and click Run. The Run tool window with console will appear.

Running Express web app:

Starting with Express 4.0 file www.js in bin folder needs to be executed to start the app. When creating a new Express web application in WebStorm 8.0.2 or higher, the required Run/Debug configuration will be created automatically. Select configuration bin/www and click Run. Now when the app is running, you can open it in browser on localhost:<app’s server port number>.

Debugging Node.js app locally

The same Run/Debug configuration can be used to debug your Node.js code.

The built-in Node.js debugger supports the latest features of V8 Debugger Protocol and allows you to step through the breakpoints, change values on the fly, evaluate expressions, and set watches.

Click the Debug button for the created Run/Debug configuration in the top right-hand corner of the IDE, from the Run menu or with the shortcut (Shift+F9 on Windows or Linux, Ctrl+D on Mac). A tool window with variables view, frames and watchers for your debug session will appear:

Debugging Node.js app that runs remotely

With Remote Node.js Debug configuration you can debug Node.js apps that are running remotely. You’ll be able to restart the debug session without restarting the app itself.
Select Remote Node.js Debug type when creating a new debug configuration, then specify the host you need to connect to and the port.

Now that the debug configuration is ready, select it from the drop-down list of configurations on the right and click Debug.

You’ll see the Debug tool window when the breakpoint is reached. You’ll be able to use full-featured debugger in the same way as if you were debugging your code locally.

Note: For remote debugging your app should be running with the parameter --debug=<port for debugging> or --debug-brk=<port for debugging>.

In Node.js you can’t access the port for debugging externally, which is why you need to configure a proxy or any other software that ensures port forwarding on the Node.js server (for an example of how to do that see stackoverflow).