mirror of
https://github.com/ProxymanApp/proxyman-windows-linux.git
synced 2026-05-04 12:21:01 +03:00
[GH-ISSUE #458] Installer .exe throws JS exception: "Could not find module node-loader" #457
Labels
No labels
Linux
bug
enhancement
enhancement
pull-request
question
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/proxyman-windows-linux#457
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 @seantiz on GitHub (Dec 10, 2024).
Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/458
Description
When trying to run the Proxyman.Setup exe for the last two releases (version 2.19.0 and version 2.18.0) the Javascript runtime within the installer will throw an exception and an alert dialog box prevents successful install.
The error message mentions not being able to find a module "node-loader" in the setup program's local data.
This error does not happen with the 2.17.0 release.
Steps to Reproduce
Download Proxyman.Setup.2.19.0.exe or Proxyman.Setup.2.18.0 on a Windows 11 machine from either the Releases page of this repository or the Proxyman for Windows site.
Double-click or run the downloaded Setup program.
Wait for it to run through the installation task and throw the exception
Current Behavior
The Setup program cannot complete its tasks. It will leave three open threads running in the background on Windows, but it will not correctly install Proxyman.
Expected Behavior
A successful installation of Proxyman on the Windows machine.
Environment
@kics223w1 commented on GitHub (Dec 13, 2024):
I can't reproduce this issue, I can install and run the application fine on Windows 11.
I test with version
2.19.0and2.18.0@seantiz commented on GitHub (Dec 13, 2024):
Ok, I will try and narrow it down over the next week or so. It is persistent behaviour on the client Windows 11 machine right now whenever upgrading to any version beyond
2.17.0