How oh-my-posh get NodeJS version

[damadorPL]

node -v
v23.1.0

return the right version that is installed globally

started to experiment with nvm for windows and installed version 20.18.0 then after few dyas uninstalled it - removed all folders created even reinstalled node again

now everytime I start powershell in node folder it show  20.18.0 ...

how it check for version of node ?

block that I use

            {
	  "type": "node",
	  "style": "diamond",
	  "powerline_symbol": "",
	  "foreground": "#FFE873",
	  "background": "",
	  "template": "  {{ .Full }} "
	}

no matter that i put in "template" always return v20 (partial or full)

there is no env folders in windows from nvm - only C:\Program Files\nodejs\ is in system variables

Win 11

nodes for python (4 global , multiple from condas and venv) always works ad return proper version but somehow cant figure how Node get version info

[lewis-yeung]

@damadorPL It's due to the (global) caching mechanism of a language segment. Please wait for #5859 which will allow disabling the cache.

[JanDeDobbeleer]

@damadorPL it's merged so you'll be able to set "cache_duration": "none" in the node segment's properties right away.

[damadorPL]

                {
		  "type": "node",
		  "style": "diamond",
		  "powerline_symbol": "",
		  "foreground": "#FFE873",
		  "background": "",
		  "template": "  {{ .Full }} ",
		  "properties": {
			"cache_duration": "none"
		  }
		}

added and now got

[damadorPL]

https://gist.github.com/damadorPL/1367c16f6b096c62646f4cc2d8c52b9e and the whole theme

[JanDeDobbeleer]

@damadorPL you need to clear the cache as well for it to get picked up: oh-my-posh cache clear

[damadorPL]

After 2nd terminal restart / and OS itself first ( context ...) error is gone, but node version still incorrect

[damadorPL]

fresh directory , fresh gh clone ...

the 20.18 version was installed previously with node version maanger for windowns - its completly uninstalled and somehow that version is still detected by omp

[JanDeDobbeleer]

@damadorPL you selected an answer, are you still experiencing the issue? If so, can you share your configuration?

[damadorPL]

oh-my-posh cache clear fixed it and I did it after previous followups - sorry for bothering