Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installer .exe throws JS exception: "Could not find module node-loader" #458

Open
seantiz opened this issue Dec 10, 2024 · 2 comments
Open
Labels
bug Something isn't working

Comments

@seantiz
Copy link

seantiz commented Dec 10, 2024

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

  1. 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.

  2. Double-click or run the downloaded Setup program.

  3. 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

  • App version: 2.19.0 or 2.18.0
  • Windows/Linux version: Windows 11
@seantiz seantiz added the bug Something isn't working label Dec 10, 2024
@kics223w1
Copy link

I can't reproduce this issue, I can install and run the application fine on Windows 11.
I test with version 2.19.0 and 2.18.0

@seantiz
Copy link
Author

seantiz commented 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.0 and 2.18.0

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants