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.

Sign up for GitHub

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

Jump to bottom

Error overlay displays webpack-internal:// links instead of file names in stack traces #146

Open
junhaoliao opened this issue Dec 2, 2024 · 1 comment · May be fixed by #147
Open

Error overlay displays webpack-internal:// links instead of file names in stack traces #146

junhaoliao opened this issue Dec 2, 2024 · 1 comment · May be fixed by #147
Labels
bug Something isn't working

Comments

@junhaoliao
Copy link
Collaborator

Bug

... when running with debug server
image

yscope-log-viewer version

969ff35

Environment

Windows 11 24H2
Node.js v22.11.0
Microsoft Edge Version 132.0.2957.11 (Official build) stable app, beta channel (64-bit)

Reproduction steps

  1. Add code that accesses an arbitrary property of a null object.
  2. Start the debug server as instructed at https://docs.yscope.com/yscope-log-viewer/main/dev-guide/building-getting-started#running-in-development
  3. Load http://localhost:3010/ in the browser and observe the files are displayed as webpack-internal:// links.
@junhaoliao junhaoliao added the bug Something isn't working label Dec 2, 2024
@junhaoliao
Copy link
Collaborator Author

As shown in below snapshot, an initial attempt to disable moduleIds: "deterministic" optimization partially fixes the issue as the file names are now displayed instead of webpack-internal:// paths; however, the line and columns reported in the overlay do not match the actual ones in the original tsx source.

image

Instead, they match the lines and columns of the webpack-transpiled sources as below snapshot shows:
image

@junhaoliao junhaoliao linked a pull request Dec 2, 2024 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
1 participant
@junhaoliao