redhat-developer / redhat-developer/lsp4ij
Please support using directory environment variables in LSP and DAP
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 344
- Forks
- 113
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 15
Description
- Basic information.
I am using mise to manage dev tools and env vars.
For example, it is using node@24.19.0 in folder/e/documents/temp/lsp4ijand but node@16.20.2 in folder/e/documents/temp/lsp4ij/useEnv.
david@lywPc /e/documents/temp/lsp4ij
$ mise ls -c
Tool Version Source Requested
go 1.26.3 (symlink) C:\Users\david\.config\mise\config.toml 1.26
java 21 (symlink) C:\Users\david\.config\mise\config.toml 21
node 24.19.0 C:\Users\david\.config\mise\config.toml 24.19.0
npm:@colbymchenry/codegraph 1.5.0 C:\Users\david\.config\mise\config.toml 1.5.0
npm:@dbx-app/mcp-server 0.4.62 C:\Users\david\.config\mise\config.toml 0.4.62
npm:@deepseek-ai/dsh 0.1.0-rc.7 C:\Users\david\.config\mise\config.toml 0.1.0-rc.7
npm:@vue/language-server 2.2.8 C:\Users\david\.config\mise\config.toml 2.2.8
npm:bash-language-server 5.6.0 C:\Users\david\.config\mise\config.toml 5.6.0
npm:stylelint-lsp 2.0.1 C:\Users\david\.config\mise\config.toml 2.0.1
npm:typescript 5.6.3 C:\Users\david\.config\mise\config.toml 5.6.3
npm:typescript-language-server 5.3.0 C:\Users\david\.config\mise\config.toml 5.3.0
python 3 (symlink) C:\Users\david\.config\mise\config.toml 3
david@lywPc /e/documents/temp/lsp4ij
$ node -v
v24.19.0
david@lywPc /e/documents/temp/lsp4ij
$ cd useEnv/
david@lywPc /e/documents/temp/lsp4ij/useEnv
$ mise ls -c
Tool Version Source Requested
go 1.26.3 (symlink) C:\Users\david\.config\mise\config.toml 1.26
java 21 (symlink) C:\Users\david\.config\mise\config.toml 21
node 16.20.2 E:\documents\temp\lsp4ij\useEnv\mise.toml 16.20.2
npm:@colbymchenry/codegraph 1.5.0 C:\Users\david\.config\mise\config.toml 1.5.0
npm:@dbx-app/mcp-server 0.4.62 C:\Users\david\.config\mise\config.toml 0.4.62
npm:@deepseek-ai/dsh 0.1.0-rc.7 C:\Users\david\.config\mise\config.toml 0.1.0-rc.7
npm:@vue/language-server 2.2.8 C:\Users\david\.config\mise\config.toml 2.2.8
npm:bash-language-server 5.6.0 C:\Users\david\.config\mise\config.toml 5.6.0
npm:stylelint-lsp 2.0.1 C:\Users\david\.config\mise\config.toml 2.0.1
npm:typescript 5.6.3 C:\Users\david\.config\mise\config.toml 5.6.3
npm:typescript-language-server 5.3.0 C:\Users\david\.config\mise\config.toml 5.3.0
python 3 (symlink) C:\Users\david\.config\mise\config.toml 3
david@lywPc /e/documents/temp/lsp4ij/useEnv
$ node -v
v16.20.2
david@lywPc /e/documents/temp/lsp4ij/useEnv
$ ll
total 3.0K
-rw-r--r-- 1 david david 25 Sep 2 21:22 mise.toml
-rw-r--r-- 1 david david 250 Sep 2 21:26 package.json
-rw-r--r-- 1 david david 78 Sep 2 21:31 test.js
david@lywPc /e/documents/temp/lsp4ij/useEnv
$
/e/documents/temp/lsp4ij/useEnv/package.json
{
"name": "useenv",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1",
"nodeVersion": "node -v"
},
"keywords": [],
"author": "",
"license": "ISC"
}
/e/documents/temp/lsp4ij/useEnv/test.js
console.log("enter test.js");
console.log(`node version: ${process.version}`);
- Npm Run/Debug Configuration is using env vars ( node@16.20.2 e.g.) under folder
useEnv.
Create Run/Debug ConfigurationuseEnvas below and run it.
- But DAP is using node@24.19.0, not the env vars under folder
useEnv.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the nested useEnv/mise.toml, package.json, test.js, and the shown DAP launch configuration. Trace how the DAP configuration resolves its working directory and environment, then verify that it selects node@16.20.2 in useEnv while retaining node@24.19.0 in the parent directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, javascript, node.js
- Domain
- developer-experience, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100