jaeger-ui: Build does not work on Windows
What happened?
- Bug: Currently, due to limited maintainer’s support for windows os, there are a few glitches inside the package.json due to which the development installation of jaeger UI fails.
- Typo: The readme.md file suggests changing the
proxyConfig.targetinside thepackage.jsonfile, though, it needs to be changed inside thevite.config.ts.
Steps to reproduce
- git clone the project into a Windows OS
- run
yarn - it would show an error after the installation of the required packages. The error says
$npm_execpath' is not recognized as an internal or external command
Expected behavior
There should be a Troubleshooting section inside the readme.md (or any other place) file which could answer the possible fix for such issues.
For example, the issue above can be resolved by manually changing the $npm_execpath to \"%npm_execpath%\"
Relevant log output
$ lerna run --stream --sort prepublishOnly
lerna notice cli v7.1.3
lerna info versioning independent
> @jaegertracing/plexus:prepublishOnly
@jaegertracing/plexus: yarn run v1.22.4
$ $npm_execpath build
@jaegertracing/plexus: '$npm_execpath' is not recognized as an internal or external command,
@jaegertracing/plexus: operable program or batch file.
error Command failed with exit code 1.
@jaegertracing/plexus: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 15 (15 by maintainers)
Commits related to this issue
- Replace $npm_execpath with yarn (#1611) ## Which problem is this PR solving? - Part of #1603 - `$npm_execpath` does not resolve on Windows ## Short description of the changes - replace `$npm_ex... — committed to jaegertracing/jaeger-ui by yurishkuro a year ago
- add wsl steps - fixes #1603 Signed-off-by: Ansh Goyal <anshgoyal1704@gmail.com> — committed to anshgoyalevil/jaeger-ui by anshgoyalevil a year ago
- Add instructions for Windows OS ## Which problem is this PR solving? - fixes #1603 - Jaeger UI has certain commands which don't run on Windows Terminal Natively, so a WSL Installation Guide is a... — committed to jaegertracing/jaeger-ui by anshgoyalevil a year ago
sgtm, please create a PR
Feel free to propose a PR with readme changes. As I understand, Win10 now allows running bash/linux without dual booting.
I re-titled the issue as general “does not work on Windows”, since it doesn’t sound like it’s just the misses in the README.
yes, please propose a PR