Automatically set up Node.js interpreter for ddev projects

[mikesnoeren]

It would be great if interpreters like Node.js automatically get set-up so we have tighter integration between PhpStorm and DDEV. Currently I still have to set this up manually (or, maybe I am doing something wrong?)

[rfay]

I know you know that DDEV already has node set up; what is it you'd like out of this plugin? https://ddev.readthedocs.io/en/latest/users/extend/customization-extendibility/#using-nodejs-with-ddev

[mikesnoeren]

Thanks, I have created an issue in the Jetbrains issue tracker.

However, even when this is resolved on my end, I think having this plugin set this up automatically for every ddev project is a great thing.

[rfay]

Please link to the issue, thanks. I agree it will be great to have the plugin set it up... when it's possible to set it up.

[mikesnoeren]

Sure, here is the issue: https://youtrack.jetbrains.com/issue/WI-71201/Issues-adding-Docker-colima-Node-interpreter

[rfay]

I added it to my watch list, but I would predict it's mostly too complicated for them to act on. To get them to act, you'll want to give them a simple docker-compose-only technique. Make a simple docker-compose.yaml which runs a simple container with node in it, and demonstrate how you can't do what you want to do there. They think of the world in the basic parts, and don't think about DDEV, etc.

[mikesnoeren]

Makes sense!

For now, I'll await their reaction and if they require more information I will do as you suggested.
For the time being I will either keep trying to get it to work, or install node locally..

I am still wondering if it is an issue with PhpStorm or if I have something misconfigured.
The only reason I need Node.js available in PhpStorm is for the Tailwind CSS plugin.

[nico-loeber]

Hey @mikesnoeren,

Thanks for this suggestion, I really like the idea!

The first Problem I do see is that PHPStorm / WebStorm does only support local and WSL installations of the node binary by default.
To configure a nodejs binary in a docker compose environment you need the plugin Node.js Remote Interpreter.
It's possible to have plugin dependencies on other plugins and they may even be optional, but it makes things a bit more complicated to implement, instead of a bundled plugin that is always available.

The second problem you talked about with @rfay already. First we need to make sure the integration is working when manually configuring it.
And now some good news, for me it is working when entering the full path to the binary /usr/bin/node to the configuration! :)

At least npm is detected in the right version, so that looks all good to me.

I guess the problem is, that /usr/bin/ is not in the PATH of the ddev container for a non login shell that phpstorm is using or something like that. But entering the full path is no problem at all for the plugin.

I will convert this to an issue so we can implement it.

[mikesnoeren]

Hi @nico-loeber,

Thank you for taking your time to help me out.

Correct me if I am wrong, but Isn't the Node.js Remote Interpreter a default plugin? I can't recall installing it.

Anyways, I do not notice any difference between setting or not setting the full Node.js interpreter path, in both cases I see a version number for NPM, but never for Node.js. And in both cases the checkmark Coding assistance for Node.js is grayed out.. When installing Node.js locally, this checkmark is the one that makes the TailwindCSS plugin work. Does that checkmark work for you? (just to verify there is a problem on my end)

Good to see as an issue for v1.1!

[nico-loeber]

• Automatically set up Node.js interpreter for ddev projects #156