I followed the instructions given here to install Remote Node.js Interpreter, even after installing and enabling the plugin the Remote Interpreter option is still not available
https://www.jetbrains.com/help/phpstorm/configure-node-js-remote-interpreter-dialog.html
Do I need to download the Ultimate edition and then install PHP and Node.js plugin or am I missing something here?
From the article:
This menu item is available only when you open the Node.js
Interpreters Dialog from the Run/Debug Configuration: Node.js.
Please use Run > Edit run/debug configurations... > Add Node.Js configuration - there will be an option to add remote interpreter
Related
I cannot open Appium inspector on Linux Ubuntu.
In the same folder I have 3 files:
Appium-Inspector-linux-2022.2.1.AppImage /
Appium-Server-GUI-linux-1.22.2.AppImage /
latest-linux.yml
When I open the Appium-Server-GUI-linux-1.22.2.AppImage file, start the server e click on the button to open Appium Ispector, it open a web page.
to fix this, it was necessary:
1: Start Appium Server
I did this, executing Appium-Server-GUI-linux-1.22.2.AppImage file.
2: Start Appium Inspector through of file Appium-Inspector-linux-2022.2.1.AppImage
3: Create the capabilities
After that, the Appium Inspector still don't open throught on Appium Server button, but it make it open and you can use.
Since the release of Appium v1.22 they have changed how the Appium Inspector works. I refer you to their official documentation on GitHub https://github.com/appium/appium-inspector, citing:
Appium Inspector is released in two formats:
As a desktop app for macOS, Windows, and Linux. You can get the most
recent published version of this app at the Releases section of this
repo. Simply grab the appropriate version for your OS and follow
standard installation procedures (but see the note below for macOS).
As a web application, hosted by Appium Pro. (It's currently a known
issue that the web version does not work on Safari). Please make sure
to read the note below on CORS as well.
If you like to work the old way, download Appium Desktop v1.21 or below.
install latest appium-inspector
open appium-inspector and insert "/wd/hub" in Remote Path
I'm currently using vscode-tomcat extension within a RHEL7 container and developing over SSH using the vscode-remote extension. However, I am unable to launch the tomcat debugger due to this unresolved issue.
"TypeError: Cannot set property 'readableListening' of undefined"
The issue only occurs when trying to launch the Tomcat debugger while doing remote SSH development. I am making an attempt to debug the issue, but I'm not sure how to debug a VSCode extension within a remote container.
Any tips would be greatly appreciated. Let me know if I can provide any additional details.
There is now documentation for all of this. Read
https://code.visualstudio.com/api/advanced-topics/remote-extensions#debugging-using-ssh
and then keep reading because further down you will find this
https://code.visualstudio.com/api/advanced-topics/remote-extensions#debugging-using-ssh
in fact read all of it, there's a lot of stuff there that initially made me think "So?" but which is vital knowledge in specialised problems.
Here's the portion relating to the immediate problem.
Debugging using SSH
Follow steps:
After installing and configuring the Remote - SSH extension, select Remote-SSH: Connect to Host... from the Command Palette (F1) in VS Code to connect to a host.
Once connected, either use File > Open... / Open Folder... to select the remote folder with your extension source code in it or select Git: Clone from the Command Palette (F1) to clone it and open it on the remote host.
Install any required dependencies that might be missing (for example using yarn install or apt-get) in a new VS Code terminal window (Ctrl+Shift+` ).
Finally, press F5 or use the Run view to launch the extension inside on the remote host and attach the debugger.
Note: You will not be able to open the extension source code folder in the window that appears, but you can open a sub-folder or somewhere else on the SSH host.
The extension development host window that appears will include your extension running on the SSH host with the debugger attached to it.
Installing a development version of your extension
Anytime VS Code automatically installs an extension on an SSH host, inside a container or WSL, or through GitHub Codespaces, the Marketplace version is used (and not the version already installed on your local machine).
While this makes sense in most situations, you may want to use (or share) an unpublished version of your extension for testing without having to set up a debugging environment. To install an unpublished version of your extension, you can package the extension as a VSIX and manually install it into a VS Code window that is already connected to a running remote environment.
Follow these steps:
If this is a published extension, you may want to add "extensions.autoUpdate": false to settings.json to prevent it from auto-updating to the latest Marketplace version.
Next, use vsce package to package your extension as a VSIX.
Connect to a codespace, development container, SSH host, or WSL environment.
Use the Install from VSIX... command available in the Extensions view More Actions (...) menu to install the extension in this specific window (not a local one).
5.Reload when prompted.
Tip: Once installed, you can use the Developer: Show Running Extensions command to see whether VS Code is running the extension locally or remotely.
I use Visual Studio Code to develop a TypeScript Node application on Windows 10, with WSL enabled.
Thanks to other threads, I'm almost able to run a VSCode task with Bash on Ubuntu on Windows.
But now I try to do the same with a launch configuration. How can I make a launch configuration to use the node executable installed in WSL instead of the one installed on Windows?
If I run this command directly in the integrated terminal, with Bash, it works :
node src/start.js
But when I press "[F5]" and start a launch configuration that runs this same file, I get an error : "Error: %1 is not a valid Win32 application". This is because the oracledb library is used and has been compiled in Bash, not in Windows.
How can I make a launch configuration use Bash to run Node?
UPDATE : I opened an issue about that on VSCode's GitHub page.
Not if sure you still need help.
open bash outside of the vs code.
then run the following command, to install node.
sudo apt install nodejs-legacy
and you should be able to run node with bash in vs code.
Is there a way to configure Node.js interpreter in Vagrant to WebStorm?
I don't need to run or debug the code via the IDE with remote tools, the only thing I really need is the IDE to be aware of the node version and installed libraries on my Vagrant server in order to have autocompletion.
I consider it should be in File -> Settings -> Languages & Frameworks -> Node.js and NPM under "Node interpreter" section.
I have Vagrant and Node.js Remote interpreter plugins installed and enabled, set up Vagrant in the IDE, but still WebStorm suggests only to add local interpreter.
If there is a solution for PhpStorm or IntelliJ, would also be appreciated, though I didn't initially plan to pay more for license.
So here is the solution I came up with.
Install some Node Version Manager on the host machine (could be nvm for Unix-like or nodist for Windows), download via it and switch to the same version of node.js (or the closest one) as I use in Vagrant and set is as interpreter in the IDE.
Not the way I like it, as I prefer to keep my host machine clean of development environments I work with. But that's the only think that comes to my mind. Would be glad to learn a better solution.
I have installed the VisualSVN server on our Windows Server 2008 plus i did connect it with Dreamweaver on other client PC.
so Dreamweaver is ready to go.
But i also want to setup the PHPStorm on other Client PC with that visualSVN.
But i want PHPStorm to use TortoiseSVN to connect to VisualSVN.
I can't find its settings page, i am new to PHPStorm, Especially to this Subversion Control thingy.
I also searched for this over web, but i cant find specific PHPStorm Setup procedure with TortoiseSVN or connecting to VisualSVN Server.
Can anyone Guide me to the Right Path?
The accepted answer is not entirely accurate. It is possible to use TortoiseSVN through PHPStorm's External Tools configurations. This does not integrate into the project navigation directly, but does allow direct file manipulation (and allows for 'blame' support - something PHPStorm's subversion lacks).
Similar functionality is used in eclipse.
Example, paths/macros's might need to be altered:
Name: SVN View Log
Program: C:\Program Files\TortoiseSVN\bin\TortoiseProc.exe
Parameters: /command:log /path:"$FileName$"
Working Directory: $FileDir$
It's impossible to connect PhpStorm to TortoiseSVN as they are doing the same thing.
Then you have two choices :
Connect PhpStorm to your SVN server with his built-in feature.
Or use TortoiseSVN
I'll recommande using PhpStorm feature as it is directly in the IDE.
You can find documentation here : https://www.jetbrains.com/phpstorm/webhelp/using-subversion-integration.html
You can actually do this very easily and it will work inside PHP Storm 8. Install Tortoise SVN and make sure to include "Command Line Tools" as part of the installation. Then you can enable External client and select the "svn.exe" as the executable. This will enable SVN 1.8 format and still work within the IDE.
My solution:
Install TortoiseSVN
Install CollabNet Subversion with command-line binaries (32 or 64-bit)
Open phpStorm
File > Settings > Version Control > Subversion
Set path for your SVN command line client
e.g.
C:\Program Files\CollabNet\Subversion Client\svn.exe
Tortoise can be used as a GUI tool, whereas CollabNet Subversion command line tool can be used with phpStorm. Enjoy!