mirror of
https://github.com/hibiken/asynqmon.git
synced 2026-04-26 09:35:49 +03:00
[GH-ISSUE #324] Need better instructions for make build on windows #442
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asynqmon#442
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @windowshopr on GitHub (Apr 20, 2024).
Original GitHub issue: https://github.com/hibiken/asynqmon/issues/324
Downloading and running the prebuilt Windows binary results in the following error in browser:
Reviewing #97 here, it seems the filepath code was designed for Linux systems, resulting in the error. I wanted to implement the fix in the static.go file myself, so I downloaded the source code for the program, made the change, then ran the
make buildcommand from a PowerShell window, resulting in the below error:...which triggered me to think "oh duh, I forgot to
npm install", so I ran that, which resulted in this next output:...so I follow the directions of using the
--forceflag, which gives me this output:Finally I try the
make buildcommand again:Same issue as before,
react-scriptsis not installed. After some digging online, the NOT ideal solution is to globally installreact-scriptsusing the commandnpm i -g react-scripts@latest --forcefollowed by themake buildagain:Something is off here, because now it seems it's sending me down a rabbit hole of installing all of the
packages.jsonpackages to a global scope, one at a time.npm installinstall is not doing what it's supposed to.Can someone try following the documentation in a Windows 10 environment and let me know what I'm missing here?
@windowshopr commented on GitHub (Apr 20, 2024):
For further context, I've also tried to manually running the backend server with
go run main.go --port 8085, and then attempting to run the frontend server withnpm run startwhich results in a giant output of issues, and a browser window that all looks like the following:Unless I'm missing something obvious here, the package just simply doesn't work on Windows.
@windowshopr commented on GitHub (Apr 20, 2024):
Oh, and I forgot that the
packages.jsonneeds to modifyexporttosetat this line in order to work on Windows: