Jaeger UI Local Setup Issue on Windows

[kirtanchandak]

Hey, I am trying to setup jaeger-ui on my local system but facing this error while installing can someone please help me out?

I have http://localhost:16686/ already setup on my system -

[albertteoh]

Just trying to understand, why do you want to setup jaeger-ui when you have http://localhost:16686/ setup?

[kirtanchandak]

http://localhost:16686/ is running from the docker container and I need to run the react code inside the jaeger-ui for the hot reload whenever I make any changes!

[kirtanchandak]

I am trying to solve this issue - jaegertracing/jaeger-ui#15 can you help me out with where can I see the preview of these copy icons, I am new to contributing to this organization!

[albertteoh]

I am trying to solve this issue - jaegertracing/jaeger-ui#15 can you help me out with where can I see the preview of these copy icons, I am new to contributing to this organization!

I guess you meant this issue: jaegertracing/jaeger-ui#1506?

http://localhost:16686/ is running from the docker container and I need to run the react code inside the jaeger-ui for the hot reload whenever I make any changes!

Thanks, makes sense. I think windows nvm doesn't recognise the .nvmrc file, but you're doing the right thing with nvm use 16 I think.

Have you tried the suggestions from the yarn install output? i.e. remove the package-lock.json file, and running in verbose mode (i.e. yarn install --verbose)?

Worth mentioning that when I run nvm use, I have the following version installed (not sure it would matter though):

$ nvm current
v16.15.0

[kirtanchandak]

Facing this error now!

[yurishkuro]

in both cases your command just fails without giving any error message ("failed with exit code 1"), so I don't have any idea how to troubleshoot it. yarn install works for me on Mac, and it works in our CI on Ubuntu.

[anikdhabal]

This is because '$npm_execpath' is not recognized as an internal or external command . Try to replace it with %npm_execpath% if you are in windows. Follow this for more info https://stackoverflow.com/questions/53883405/npm-execpath-isnt-recognized-as-an-internal-or-external-command-program-or

[yurishkuro]

would it help if we replaced this line with yarn build?

    "prepublishOnly": "$npm_execpath build",

https://github.com/jaegertracing/jaeger-ui/blob/c179d57cff329726ebbd8d20ddc6b12a100a46ca/packages/plexus/package.json#L68

It's the only place that uses $npm_execpath

[anikdhabal]

Then problem occurs 'NODE_ENV' is not recognized.