Eslint support? (NodeJS)

[mandrasch]

Hey,

just wanted to ask if eslint fully works via this (awesome) integration plugin in PhpStorm?

As far as I understand it runs via the NodeJS interpreter
https://www.jetbrains.com/help/phpstorm/eslint.html#ws_node_docker_lint

I see this:

But also get this, since I'm using colima:

#83 (Don't know if this is related)

Config:

I'm running on

• colima version 0.5.5
• ddev version v1.22.1
• OSX 13.5.2
• PhpStorm: 2023.2.1

Thanks very much for information and thanks very much for providing this plugin!

Cheers!

[mandrasch]

Okay turns out this works, but is not a good idea (yet)

When a TS file is open(!), Eslint service will try to connect & starts web containers, interfering with ddev start which can lead to timeout issues. and it really slows down your phpstorm, at least thats what I was experiencing.

In the meantime I switched to local node again

More info: https://discord.com/channels/664580571770388500/1161952380062011422

Hi @nico-loeber, I just had one question regarding this - what is does this automatic configuration "nodejs interpreter" mean? And what settings should I see in NodeJS interpreter settings? Or is there an override?

thanks for providing the ddev plugin!

[nico-loeber]

Hey @mandrasch,
the plugin does provide a node interpreter configuration. You should find it in File | Settings | Languages & Frameworks | Node.js.
This interpreter configuration is used for running yarn / npm and for executing other node based tooling you might use in your frontend workflow. There are currently some limitations that might include eslint. See #156 for more detail.
The interpreter is configured to use the existing and running ddev container, so it should not start a new container like you described.
The current limitations come from PHPStorm not fully supporting remote node interpreters, so for now you might need to use a local installation and work with that one until the support is improved.

You can check if you make it to configure PHPStorm to use the ddev container for eslint manually. If this works, we can then do this configuration automatically by the plugin.
Otherwise I would like to encourage you to open a ticket for Webstorm/PHPStorm.

[rfay]

The thing is here @nico-loeber that it's creating a large bug that the ddev-intellij-plugin is adding a nodejs configuration that uses the container-based node. I recommend that until Jetbrains supports "exec" for node (and several other things) that this plugin not create that setup, as it can do nothing but trouble. There are a few existing issues about this in youtrack, for example https://youtrack.jetbrains.com/issue/WEB-53172

[iamntz]

hey guys, i figured out something that may help others too: make Node and phpstorm work together (though I'm not sure how it plays with eslint, but it worth a try)

some while ago i was very confused about how should phpstorm be configured in order to have node inside docker. unfortunately, phpstorm is kind of limited in this regards (i.e. doesn't allow to reuse a container, but only to start it) and (probably) it will take some years to have it fixed. so here is a little workaround: add a new node remote interpreter with node:18-alpine as image name (or whatever version you need).

this won't use the ddev version but it will use a docker container. with a bit of a trickery, you could use ddev npm for managing packages and this remote interpreter for... stuff.

it took me a while to figure out that this is possible, i'm sure it may have some limitations, but for what i need it is good enough.

discussion also started here

[mandrasch]

Hey! thanks for sharing! nice workaround if I don't want to use the nodejs version on my host computer / switch faster between node versions 👍 if I have time in the next weeks I'll check with eslint.

[iamntz]

@mandrasch my goal was to have the the ability to debug some scripts, so I have no idea how this works for eslint.

But for debugging, it works :)

[iamntz]

Update: I tested and I can confirm that the method above works for eslint and prettier.