eclipse-wildwebdeveloper / eclipse-wildwebdeveloper/wildwebdeveloper

Let user select a version a `runtimeExecutable` path to specific node.js in Node Launch Configuration

Open
#335 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
201
Forks
76
Avg merge
4d 7h
Merged PRs (30d)
21

Description

WWD needs a NodeJS to run language servers, and also to execute NodeJS launch configurations. Currently, there's not much control over which NodeJS is used. You either have to set org.eclipse.wildwebdeveloper.nodeJSLocation in eclipse.ini or add NodeJS to your PATH. This isn't very flexible, and is problematic because I work on multiple projects that use different versions of NodeJS.

Today, I'm just setting nodeJSLocation and living with the fact that language servers are run with a different NodeJS than the projects are built with. And I'm using JSDT's NodeJS launch config to build the projects, since JSDT allows me to select which NodeJS I want.

It would be nice if WWD provided a workspace-level config option to set which NodeJS to use, and used the specified NodeJS to start language servers and to run NodeJS launch configs.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the existing org.eclipse.wildwebdeveloper.nodeJSLocation setting, language-server startup, and the NodeJS launch configuration. Done means a workspace-level Node.js selection is honored for both language servers and NodeJS launch configurations, including projects that use different Node.js versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
developer-experience
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.